ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Dart's sound null safety prevents runtime crashes by distinguishing nullable (String?) from non-nullable (String) types at compile time. Use late for deferred initialization, but avoid excessive ! assertions.
Ceylon rejects direct dereference of nullable types. Use exists, else, and nonempty to handle null safely, with scoping limits and toolchain checks.
Enabling nullable reference types in legacy .NET projects triggers hundreds of warnings. Learn how to migrate systematically using flow analysis and proper null handling patterns.
Kotlin treats unannotated Java types as platform types, deferring null failures to runtime. Annotate Java APIs and enable -Xjsr305=strict to move enforcement to compile time.
Make every String|Integer variant explicit in Ceylon so the compiler catches missing branches before runtime.
Crystal's ? suffix makes nilability part of the type system, turning null-reference crashes into compile-time errors. Control-flow refinement narrows types after nil checks, and &. handles optional values inline. Trade-off: nilables spread through generics, increasing verbosity.
Learn how Dart's Sound Null Safety eliminates NullPointerExceptions by shifting null checks from runtime to compile-time, and how to use 'late' and '?' effectively.
Learn how to migrate a Dart project to sound null safety, with version‑specific steps, a worked example, trade‑offs, and a verification checklist.
NullReferenceException remains common because reference types were nullable by default. Enabling nullable reference types in C# shifts null checks to compile time, with adoption patterns, a worked DTO example, and trade‑offs for .NET teams.
flutter
dotnet
kotlin
crystal
csharp