sure
I mean with a modern typesystem used correctly
and I do mean *static*: so, actually erased in the machine code
I mean with a modern typesystem used correctly
and I do mean *static*: so, actually erased in the machine code
March 30, 2025 at 10:06 PM
sure
I mean with a modern typesystem used correctly
and I do mean *static*: so, actually erased in the machine code
I mean with a modern typesystem used correctly
and I do mean *static*: so, actually erased in the machine code
tfw you have a super modern typesystem so you can make your code "very general"
youtu.be/gKNJKce1p8M?...
youtu.be/gKNJKce1p8M?...
Procedural Generation using Constraint Satisfaction
Learn how to use constraint satisfaction algorithms to generate a wide variety of procedural content, including maps, plants, and textures.
youtu.be
July 22, 2024 at 11:01 PM
tfw you have a super modern typesystem so you can make your code "very general"
youtu.be/gKNJKce1p8M?...
youtu.be/gKNJKce1p8M?...
Eh ben... C'est pas demain que le typesystem de Typescript deviendra sound...
May 14, 2025 at 6:03 AM
Eh ben... C'est pas demain que le typesystem de Typescript deviendra sound...
my gripe with the #elixirlang typesystem is that if you want checking against structs in your function header, you must specify the struct module, which creates an extra map lookup in the function call
January 3, 2025 at 5:22 PM
my gripe with the #elixirlang typesystem is that if you want checking against structs in your function header, you must specify the struct module, which creates an extra map lookup in the function call
The typesystem does an amazing job at eliminating a huge number of bugs (including null pointer bugs!) at compile time, the heavily functional under the hood semantics are great, nice overloading, and the debugger in InteliJ rocks.
January 20, 2024 at 2:47 PM
The typesystem does an amazing job at eliminating a huge number of bugs (including null pointer bugs!) at compile time, the heavily functional under the hood semantics are great, nice overloading, and the debugger in InteliJ rocks.
we surface the typesystem violation as an error, the hard part is explaining to customers why they should stop doing that
August 21, 2024 at 5:18 PM
we surface the typesystem violation as an error, the hard part is explaining to customers why they should stop doing that
Yeah I mean I am a type fascist in Python but Haskell’s more type centric approach seems like a good candidate for the models — super fast feedback loops, a culture of embedding as much checkable logic into the typesystem &c. Hmm.
June 2, 2025 at 10:30 PM
Yeah I mean I am a type fascist in Python but Haskell’s more type centric approach seems like a good candidate for the models — super fast feedback loops, a culture of embedding as much checkable logic into the typesystem &c. Hmm.
For those cases you have `expect`, where you give the reason why you expect not a None. And you could also do a match and an unreachable (or unreachable_unchecked!). Or even better, encode it in the typesystem.
unwrap is generally used for the "I can't be bothered to handle this rn" case
unwrap is generally used for the "I can't be bothered to handle this rn" case
June 15, 2025 at 12:57 PM
For those cases you have `expect`, where you give the reason why you expect not a None. And you could also do a match and an unreachable (or unreachable_unchecked!). Or even better, encode it in the typesystem.
unwrap is generally used for the "I can't be bothered to handle this rn" case
unwrap is generally used for the "I can't be bothered to handle this rn" case
I think JS / TS gives you the opportunity for tighter connection between the frontend and Backend, because they share the same language and typesystem
January 13, 2025 at 10:32 PM
I think JS / TS gives you the opportunity for tighter connection between the frontend and Backend, because they share the same language and typesystem
It's not like they've done away with words. If anything, they've enhanced them with an updated font and typesystem. Love the ligature swoosh between the R and the S.
November 18, 2024 at 5:28 PM
It's not like they've done away with words. If anything, they've enhanced them with an updated font and typesystem. Love the ligature swoosh between the R and the S.
If P /= NP, the subset of the type of functions of at most length O(l) in some polynomial typesystem is a proper subset of the set of the subset of the type of functions of at most length O(l) in the simply typed lambda calculus.
April 24, 2025 at 1:55 AM
If P /= NP, the subset of the type of functions of at most length O(l) in some polynomial typesystem is a proper subset of the set of the subset of the type of functions of at most length O(l) in the simply typed lambda calculus.
react-book.melange.re/intro/
I love #ocalm.
it has many superpowers
- #soundcomplete and #strong #typesystem with #typeinference
- #algebraiceffects
- #algebraicdatatypes
- #GADT
- #patternmatching
- pragmatic by default #immutanbility
- pragmatic and optional laziness
I love #ocalm.
it has many superpowers
- #soundcomplete and #strong #typesystem with #typeinference
- #algebraiceffects
- #algebraicdatatypes
- #GADT
- #patternmatching
- pragmatic by default #immutanbility
- pragmatic and optional laziness
Melange for React Developers | Melange for React DevsGitHubGitHub
A project-based, guided introduction to Melange and its ecosystem for React developers
react-book.melange.re
October 8, 2024 at 7:39 AM
react-book.melange.re/intro/
I love #ocalm.
it has many superpowers
- #soundcomplete and #strong #typesystem with #typeinference
- #algebraiceffects
- #algebraicdatatypes
- #GADT
- #patternmatching
- pragmatic by default #immutanbility
- pragmatic and optional laziness
I love #ocalm.
it has many superpowers
- #soundcomplete and #strong #typesystem with #typeinference
- #algebraiceffects
- #algebraicdatatypes
- #GADT
- #patternmatching
- pragmatic by default #immutanbility
- pragmatic and optional laziness
Typescript typesystem is just crazy... to think that they can solve the sudoku before the program execute 😂 (Or make doom run within TS typesystem)
May 21, 2025 at 1:43 PM
Typescript typesystem is just crazy... to think that they can solve the sudoku before the program execute 😂 (Or make doom run within TS typesystem)
maldita hora q apis "restful" viraram o padrao. na pratica tu tem q escrever um typesystem em cima dessa merda
October 7, 2024 at 5:20 PM
maldita hora q apis "restful" viraram o padrao. na pratica tu tem q escrever um typesystem em cima dessa merda
Theme 4: A point of discussion was whether Rust's type system is affine or uses uniqueness types. This impacts how references are managed and their copyability, revealing subtle aspects of Rust's ownership system. #Typesystem 5/5
July 10, 2025 at 7:00 AM
Theme 4: A point of discussion was whether Rust's type system is affine or uses uniqueness types. This impacts how references are managed and their copyability, revealing subtle aspects of Rust's ownership system. #Typesystem 5/5
To be honest, I barely care for raw compile time for our project, I mostly hope that elixir-ls will give diagnostics earlier as a consequence of that.
But what I am eager about is to see what new edge cases are uncovered by the enhenced typesystem.
But what I am eager about is to see what new edge cases are uncovered by the enhenced typesystem.
June 10, 2025 at 12:00 PM
To be honest, I barely care for raw compile time for our project, I mostly hope that elixir-ls will give diagnostics earlier as a consequence of that.
But what I am eager about is to see what new edge cases are uncovered by the enhenced typesystem.
But what I am eager about is to see what new edge cases are uncovered by the enhenced typesystem.
Lightweight, Linux-compatible kernel, written in Rust to leverage the safety of the typesystem. Aiming to remove as much legacy as possible while supporting most usecases.
oshub.org/projects/mae...
#osdev #oshub #maestro
oshub.org/projects/mae...
#osdev #oshub #maestro
maestro on OSHub
Lightweight, Linux-compatible kernel, written in Rust to leverage the safety of the typesystem. Aiming to remove as much legacy as possible while s...
oshub.org
October 21, 2025 at 6:24 AM
Lightweight, Linux-compatible kernel, written in Rust to leverage the safety of the typesystem. Aiming to remove as much legacy as possible while supporting most usecases.
oshub.org/projects/mae...
#osdev #oshub #maestro
oshub.org/projects/mae...
#osdev #oshub #maestro
at least the typesystem will help me sort this out /s
May 21, 2024 at 11:14 PM
at least the typesystem will help me sort this out /s
I'm so frustrated with the state of art options in programming langs.
I want:
- good performance so I can build serious backends in it
- good typesystem
- good tooling (compiler, crosscompiles, formatters, etc)
And I can find 2-out-of-3 in a couple places. But no 3/3.
I want:
- good performance so I can build serious backends in it
- good typesystem
- good tooling (compiler, crosscompiles, formatters, etc)
And I can find 2-out-of-3 in a couple places. But no 3/3.
June 7, 2024 at 8:26 AM
I'm so frustrated with the state of art options in programming langs.
I want:
- good performance so I can build serious backends in it
- good typesystem
- good tooling (compiler, crosscompiles, formatters, etc)
And I can find 2-out-of-3 in a couple places. But no 3/3.
I want:
- good performance so I can build serious backends in it
- good typesystem
- good tooling (compiler, crosscompiles, formatters, etc)
And I can find 2-out-of-3 in a couple places. But no 3/3.
Rust was really remarkable for taking an affine typesystem and making it not only something nonacademic programmers can wrap their heads around, but really actively want to use.
February 19, 2025 at 4:22 AM
Rust was really remarkable for taking an affine typesystem and making it not only something nonacademic programmers can wrap their heads around, but really actively want to use.
Just merged a refactoring ensuring the code works on a hash value, and not any bytes value, by wrapping said value in a #rust enum (similar #fsharp DU). Fearless refactorings are so enjoyable, don't want to imagine doing it without assistance of the typesystem! github.com/asfaload/asf...
32 wrap all hash values in an enum by rbauduin · Pull Request #33 · asfaload/asfasign
github.com
September 25, 2025 at 3:34 PM
Just merged a refactoring ensuring the code works on a hash value, and not any bytes value, by wrapping said value in a #rust enum (similar #fsharp DU). Fearless refactorings are so enjoyable, don't want to imagine doing it without assistance of the typesystem! github.com/asfaload/asf...
lisp doesn't have a good typesystem and it's not always trivial to do pattern matching
haskell makes it too difficult sometimes when more than one monad is happening or when you want to define more complex data structures (a json for instance)
haskell makes it too difficult sometimes when more than one monad is happening or when you want to define more complex data structures (a json for instance)
June 25, 2024 at 11:15 AM
lisp doesn't have a good typesystem and it's not always trivial to do pattern matching
haskell makes it too difficult sometimes when more than one monad is happening or when you want to define more complex data structures (a json for instance)
haskell makes it too difficult sometimes when more than one monad is happening or when you want to define more complex data structures (a json for instance)
I mean, get the concept of cancellation(-safety) into the typesystem
January 31, 2025 at 10:23 PM
I mean, get the concept of cancellation(-safety) into the typesystem
Ok, so, expressivity in the typesystem, maybe reasoning about deadlock-freedom, etc.
Any foreseeable advantages wrt low level optimizations? Like, can I optimize the code *between* the synchronization points better if I know them at the type system level at compile time?
Any foreseeable advantages wrt low level optimizations? Like, can I optimize the code *between* the synchronization points better if I know them at the type system level at compile time?
January 18, 2025 at 3:06 PM
Ok, so, expressivity in the typesystem, maybe reasoning about deadlock-freedom, etc.
Any foreseeable advantages wrt low level optimizations? Like, can I optimize the code *between* the synchronization points better if I know them at the type system level at compile time?
Any foreseeable advantages wrt low level optimizations? Like, can I optimize the code *between* the synchronization points better if I know them at the type system level at compile time?