Earlier quoted context omitted.
I have never heard about this before. What exactly would happen to broken code? For example, would it skip the equivalent of the broken source line, or would it stub out a function altogether or what?
Literally that, it would throw exceptions with the compiler error. And as a sibling comment mentioned and I had forgotten -- it would allow for hotpatching code at runtime as you fixed compiler errors. You could literally start the skeleton of a webserver and gradually add functionality to it without recompiling and it would mostly "just work". Certain changes would require the app to be restarted.
Hazel: A live functional programming environment featuring typed holes
21–30 of 88 posts
Re: Hazel: A live functional programming environment featuring typed holes
#22Elm/ML is an interesting choice of mis-mash & a subtle slap in the face of Haskell? (Which on the surface is far more like Elm than ML is).
I would take that to mean "strict evaluation" and "simple type system"
biggest reason more haskelley syntax didnt/hasnt happen/ed is the current syntax engine does not support significant indentation. hazel concrete syntax isn't stable yet though we're also thinking seriously about semi-colons
Re: Hazel: A live functional programming environment featuring typed holes
#23Haskell has type holes. There are plugins that give you code actions to complete them, split case, etc. I love type holes. Agda has them too and they're more powerful there: https://agda.readthedocs.io/en/latest/language/lexical-struc...
Re: Hazel: A live functional programming environment featuring typed holes
#24Haskell has type holes. There are plugins that give you code actions to complete them, split case, etc. I love type holes. Agda has them too and they're more powerful there: https://agda.readthedocs.io/en/latest/language/lexical-struc...
Typescript has a hole type too implemented in fp-ts and effect-ts. Super useful for when you don't know what are you missing and get a type signature for it. It's mostly useful for when you declare some `const foo: (bar: Bar) => Whatever` and in the midst of your implementation you don't know what you're missing. Requires an advanced level in TS to be used to the max. https://gcanti.github.io/fp-ts/modules/function.t…
we (team hazel) recently used that device in our typescript version of a hazel setup for typed-hole-contextualized code completion as described in https://dl.acm.org/doi/10.1145/3689728
Re: Hazel: A live functional programming environment featuring typed holes
#25Earlier quoted context omitted.
I use IntelliJ now and I definitely miss this feature of Eclipse.
Why? What did you miss about it? I'm asking as I prefer strict compilers that force me to handle all cases.
In an ideal world, the codebase would be modular and testable and all those good things but I work in a large enterprise dev team and some of the codebase is many (many) years old and it's no longer feasible to refactor it into anything like what would be needed to allow the code to be modularized in such a way that would obviate the necessity to do the above.
Re: Hazel: A live functional programming environment featuring typed holes
#26Earlier quoted context omitted.
I use IntelliJ now and I definitely miss this feature of Eclipse.
Why? What did you miss about it? I'm asking as I prefer strict compilers that force me to handle all cases.
Re: Hazel: A live functional programming environment featuring typed holes
#27This is semi-related to one of the killer features of Eclipse that never really made it into any large-scale systems: the ability to run incomplete or broken code. The Eclipse Compiler for Java had a special feature that it could generate bytecode for nearly any file, including those that were utterly broken. It would mostly work, and you could incrementally work on unit tests alongside the code being developed. It w…
It does sound like a good feature though - very few languages have opt-out type checking. This is much better than opt-in IMO.
Re: Hazel: A live functional programming environment featuring typed holes
#28This is semi-related to one of the killer features of Eclipse that never really made it into any large-scale systems: the ability to run incomplete or broken code. The Eclipse Compiler for Java had a special feature that it could generate bytecode for nearly any file, including those that were utterly broken. It would mostly work, and you could incrementally work on unit tests alongside the code being developed. It w…
Re: Hazel: A live functional programming environment featuring typed holes
#29Re: Hazel: A live functional programming environment featuring typed holes
#30And it had a release today.
https://www.noodlesoft.com/release_notes
Seems rough to jump on a name that's been in continuous use for that long. Would it be hard to add another word to make it easier to disambiguate?