Live data from Hacker News

Viewing profile — yoneda

yoneda

HN member
Joined
Fri, Feb 12, 2021, 3:51 AM UTC
HN karma
131
Public activity
14 items

About yoneda

No profile information was provided.

Recent public activity

  1. comment
    Comment #37348451

    The "obvious" observation from the article is: > Obviously, λx.M should be seen as a sort of function The fact that lambdas can be seen as a syntax for describing functions (or fun…

  2. comment
    Comment #27027172

    > Quite a few times I was surprised that Rust breaks with some old patterns that were copied over and over in the last 50 years or so. For example: "match" instead of "switch", or …

  3. comment
    Comment #26959163

    Yes, Java's type system "so weak". Just because many other popular languages have similarly weak type systems doesn't make them less weak. Also, as a long-time Haskell user, I can …

  4. comment
    Comment #26867923

    Logically speaking, Rust's "enums" are neither enums (in the traditional sense) nor unions. They are tagged unions / disjoint unions / variants / coproducts / algebraic data types.…

  5. comment
    Comment #26832027

    I generally agree, except the part about the low risk of runtime surprises. Java's type system is so weak that it doesn't even prevent null from inhabiting almost every type. The p…

  6. comment
    Comment #26650580

    Huh, so equality isn't transitive in Go. Yikes.

  7. comment
    Comment #26472096

    > It’s important to understand that this is a big problem. If a type system is Turing complete, than it either has to be inconsistent or incomplete. In other words it either must a…

  8. comment
    Comment #26281862

    This is a great writeup, and I just want to offer a counterpoint regarding the eager vs. lazy trade-offs. I found this article really helpful for explaining why laziness is importa…

  9. comment
    Comment #26219799

    > but can't typically "find their own way" to the proof of a theorem That's not what proof assistants like Lean and Coq are about. Sure, they can automate some trivial things, but …

  10. comment
    Comment #26198124

    Seems like you didn't read my comment in its entirety. I acknowledged that the article discusses exhaustiveness checking, so you don't need to point that out to me. I didn't make a…

  11. comment
    Comment #26191337

    One of my favorite qualities of the Haskell community is how honest they are about the weaknesses of the ecosystem (we often discuss issues like these, e.g., on r/haskell or in mai…

  12. comment
    Comment #26191305

    The primary advantage of proper pattern matching compared to ad hoc "instanceof" checks is exhaustiveness checking. I love the comfort in knowing the compiler will tell me all the …

  13. comment
    Comment #26162169

    On the contrary, I find myself more productive in languages that do not have pervasive null because then I don't have to manually reason about which values might be null.

  14. story