7h3kk1d

Never in TypeScript is the equivalent of "bottom" where a value can never appear. The type holes in hazel are for incomplete types (during development) and work more like the any type in typescript where they are consistent with every value.

I don't think you do. The --in param on svg-term-cli worked for me locally.

I'm quite sure my grandma could not. You can make the argument these people aren't intelligent but I think that's a contrived argument.

There's sentient humans who can't beat the first generation pokemon games.

I agree with regards to checked exceptions. Unfortunately Java doesn't support any form of polymorphism over thrown exceptions so it makes your code much harder to reuse. In languages that support polymorphic effects I imagine this is less of a concern.

""Make illegal states unrepresentable" is way too expensive to implement."

This has not been my experience. The speed increase in development not having to worry about the unrepresentable cases have been very valuable. In addition as requirements change migrating old data hasn't been a huge concern. For code changes refactoring the types helps address new cases as well.

I'm not sure I understand your point. Typed holes aren't trying to get rid of the concept of interfaces or well designed abstractions. Rather they aim to help deal with incomplete programs that are still under development.

If you put the cursor on it you'll see an error message at the bottom. In this case the case expression is inexhaustive because it's only handling lists of size 0, 1, and 2.

You can play with it at https://hazel.org/build/dev/ but programs don't "crash" when they're incomplete so "1 + 5 + ?" will evaluate to "6 + ?" in the editor. So your program can evaluate as far as possible with the holes. If you're using Java and throw NotImplementedException you lose all context to what did work.

Hazel will also run incomplete programs around holes. Most untyped languages will just crash as soon as something is incomplete.

I think the above commenter is more critiquing the notion of relying on intuition all together.

Do they have consumer app versions?

Most are, but I have definitely worked on projects that weren't

Possibly add a merge trees feature?

I'd rather find a better long term fit quicker than have a pleasant process when looking.

I think the point is to consciously acknowledge what you're doing needs a side effect. It's similar with mutable state. Both state and side effects are completely necessary but should be isolated and controlled through known constructs.