Do you still have to enable OverloadedStrings to make string literals not terrible?
-
-
-
Replying to @brendanzab @glenathan and
Dang, it's been 11 years. You'd think by now it'd just be default
1 reply 0 retweets 1 like -
Replying to @sgrif @glenathan and
Yeah. I really love the approach of 'simple core' then 'let a thousand extensions bloom', but they've waited long enough to turn on some of them by default...
2 replies 0 retweets 0 likes -
Replying to @brendanzab @glenathan and
Extensions have to be in the compiler itself too, right? I can't just write a package that adds a new one?
1 reply 0 retweets 0 likes -
Replying to @sgrif @glenathan and
Right. But they are 'firewalled' off from the core language, which is very simple.
1 reply 0 retweets 0 likes -
Replying to @brendanzab @sgrif and
I could actually be wrong though- I feel like I gave seen third-party extensions that you can add with a pragma. They might be more limited though.
1 reply 0 retweets 0 likes -
Replying to @brendanzab @sgrif and
Here's an example! https://github.com/ocharles/what-it-do … - just seems to be a syntax thingo though, not actually extending the typechecker. But I guess the overloaded strings thing is just a syntax thingo anyway (just wraps literals in calls to `fromString`).
1 reply 0 retweets 0 likes -
Replying to @brendanzab @glenathan and
So basically Rust extensions (but looks like run closet to when lints are)
1 reply 0 retweets 0 likes -
Replying to @sgrif @glenathan and
Nah, I think this is more run after parsing and before type checking. Possibly before/after desugaring.
1 reply 0 retweets 0 likes
That Readme claims it has access to the type checker and can know if any expression has an instance of show
-
-
Replying to @sgrif @glenathan and
Oooooh, serves me right for not reading closely. And helps to read the documentation: https://downloads.haskell.org/~ghc/master/users-guide/extending_ghc.html#compiler-plugins …
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.