News for hackers. Stuff that matters.

A comment on The Next Step for Generics. Parent comment

Re:The Next Step for Generics by waheoo on Tuesday June 16, 2020 @11:16PM (#23547354)
Well if a functions first run is in production youve got other problems. The idiot ref would be right.
[ Parent | on HN ]
Re:The Next Step for Generics by pansa2 on Wednesday June 17, 2020 @02:54AM (#23548546)
“Compile-time and runtime are less relevant notions than before-shipping and after-shipping” - Rich Hickey

https://twitter.com/richhickey/status/1063086406980026370

[ Parent | on HN ]
Re:The Next Step for Generics by bonestormii_ on Wednesday June 17, 2020 @03:39AM (#23548856)
Hehe. But has anyone ever shipped code that won't compile? I think not.

A compile time error is a caught error. A run time error may be, or perhaps not.

[ Parent | on HN ]
Re:The Next Step for Generics by logeprog on Thursday June 18, 2020 @02:57AM (#23560495)
This!
[ Parent | on HN ]
Re:The Next Step for Generics by bonestormii_ on Tuesday June 16, 2020 @11:59PM (#23547614)
It ran fine with all the file types we tested! A dependency loads the file into a custom type, but it handles this file type differently! Now it's a stinky old NoneType. :( :( :(
[ Parent | on HN ]