Bluesky: January 13, 2025 at 3:31:00 PM UTC

from blog Zach Leatherman’s Activity Feed, | ↗ original
“tsc does not follow semantic versioning, so even minor updates can introduce changes to type checking that may break existing code.” — @satanacchio.bsky.social https://satanacchio.hashnode.dev/everything-you-need-to-know-about-nodejs-type-stripping
This is a short summary. ↗ Open original to view full content

Related

Using tsc as a Codebase Doctor
Chris' Full Stack Blog RSS Feed | original ↗
A workaround for Rust's lack of structural subtyping
nickb.dev | original ↗
A type checking error in Elixir 1.18
Jonas Hietala | original ↗
CCI and versioning
baby steps | original ↗
[elsewhere] True Myth v8.4.0
Sympolymathesy, by Chris Krycho | original ↗
The 'Tootsie Pop' model for unsafe code
baby steps | original ↗
Thoughts on trusting types and unsafe code
baby steps | original ↗
An experimental new type inference scheme for Rust
baby steps | original ↗
[elsewhere] True Myth v8.2.0—Now With a Task Type!
Sympolymathesy, by Chris Krycho | original ↗
Borrowing errors
baby steps | original ↗

More from Zach Leatherman’s Activity Feed

Mastodon: January 14, 2025 at 6:13:20 PM UTC
14 Jan 2025 | original ↗

I am very unserious but also simultaneously extremely seriousmultitudes wish they contained me

Mastodon: January 14, 2025 at 5:36:16 PM UTC
14 Jan 2025 | original ↗

your nose is 3d printer for boogers, think about it

Mastodon: January 13, 2025 at 5:41:53 PM UTC
13 Jan 2025 | original ↗

we’ve formalized this process here: https://www.11ty.dev/blog/certification/

Mastodon: January 12, 2025 at 11:33:45 PM UTC
12 Jan 2025 | original ↗

9 y/o tried to say that I was middle aged but instead said that I was from the Middle Ages

Bluesky: January 10, 2025 at 9:36:00 PM UTC
10 Jan 2025 | original ↗

mistakes were made mistakes were fixed