News for hackers. Stuff that matters.

A comment on Why Kotlin is my next programming language (2015). Parent comment

Re:Why Kotlin is my next programming language (2015) by winstonewert on Monday June 20, 2016 @12:53AM (#11936120)
Do you need a test to verify that your compiler correctly checks the type signature? (Actually, that could be occasionally useful in the face of implicit conversions)
[ Parent | on HN ]
Re:Why Kotlin is my next programming language (2015) by bbcbasic on Tuesday June 21, 2016 @06:37PM (#11950016)
You can't get true 100% coverage* on digital hardware. (on quantum maybe!) so what to test or not is always a judgement call. Most of the time I'd assume the software stack is trustworthy but if you are doing something extreme you may want to test the compiler or even formally prove the compiler works as expected.

* true as in all possible inputs and outputs rather than merely all code paths

[ Parent | on HN ]
Re:Why Kotlin is my next programming language (2015) by winstonewert on Tuesday June 21, 2016 @07:38PM (#11950366)
Perhaps a better way to ask my question: do you write a test to make sure your type signature was correct?
[ Parent | on HN ]
Re:Why Kotlin is my next programming language (2015) by eropple on Monday June 20, 2016 @01:21PM (#11939477)
My compilers have test suites.
[ Parent | on HN ]
Re:Why Kotlin is my next programming language (2015) by winstonewert on Monday June 20, 2016 @04:32PM (#11941304)
And the compiler that generates the assert also has a test suite for that.
[ Parent | on HN ]