Explore >> Select a destination
|
You are here 
|
rcoh.me | ||
| | | | |
www.dalkescientific.com
|
|
| | | | | ||
| | | | |
nurkiewicz.com
|
|
| | | | | When choosing or learning a new programming language, type system should be your first question. How strict is that language when types don't really match? Will there be a conservative, slow and annoying compiler? Or maybe a fast feedback loop, often resulting in crashes at runtime? And also, is the language runtime trusting you know what you are doing, even if you don't? Or maybe it's babysitting you, making it hard to write fast, low-level code? Believe it or not, I just described static, dynamic, weak and strong typing. | |
| | | | |
swtch.com
|
|
| | | | | ||
| | | | |
www.ryanliptak.com
|
|
| | | An introduction to a recent addition to Zig's standard library that allows for checking that any allocation failures are handled without introducing memory leaks, etc. | ||
