Latest Tech News

Stay updated with the latest in technology, AI, cybersecurity, and more

Filtered by: nullable Clear Filter

Nullable vs. Nullable in C#

Nullable vs nullable in C# One of the most unfortunate parts of the nullability narrative in C# is the reuse of the T? syntax to denote two completely separate concepts for value types and reference types. This leads to some odd and confusing behaviour. As you may know, nullable value types is a much older concept than nullable reference types. Nullable value types were introduced in C# 2.0, whereas nullable reference types came in C# 8.0. And they’re not the same. Nullable isn’t nullable. Fo

Show HN: Typed-arrow – compile‑time Arrow schemas for Rust

typed-arrow provides a strongly typed, fully compile-time way to declare Arrow schemas in Rust. It maps Rust types directly to arrow-rs typed builders/arrays and arrow_schema::DataType — without any runtime DataType switching — enabling zero runtime cost, monomorphized column construction and ergonomic ORM-like APIs. Why compile-time Arrow? Performance: monomorphized builders/arrays with zero dynamic dispatch; avoids runtime DataType matching. matching. Safety: column types, names, and nullab

Nullable but not null

When working on backend applications, especially those with evolving database schemas, it’s common to see a recurring pattern: A new field is added to a model. To avoid locking the table during the migration, the field is added as nullable. The application logic is updated to start filling in this field. A backfill job runs to populate the existing records. The field is left as nullable. People often forget the final step which is updating the schema to make the field non-nullable once the dat

nullable but not null

When working on backend applications, especially those with evolving database schemas, it’s common to see a recurring pattern: A new field is added to a model. To avoid locking the table during the migration, the field is added as nullable. The application logic is updated to start filling in this field. A backfill job runs to populate the existing records. The field is left as nullable. People often forget the final step which is updating the schema to make the field non-nullable once the dat