You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, if we define a type twice the last definition wins. It would be nice if instead we could blow up at compile time, either with a warning or (preferably) an error, because it's never going to be what someone wants to do. I wasted an hour debugging until I found that I'd double-defined a type with the same name :-\ Not the fault of absinthe, but it seems like it would be nice to save all the "future-me"s that time :)
The text was updated successfully, but these errors were encountered:
Presently, if we define a type twice the last definition wins. It would be nice if instead we could blow up at compile time, either with a warning or (preferably) an error, because it's never going to be what someone wants to do. I wasted an hour debugging until I found that I'd double-defined a type with the same name :-\ Not the fault of absinthe, but it seems like it would be nice to save all the "future-me"s that time :)
The text was updated successfully, but these errors were encountered: