3 ms·
IDK, I still miss Rust's strictness and exhaustive enum matching.
by throw-the-towel 8mo ago
IDK, I still miss Rust's strictness and exhaustive enum matching.
- socalgal2 8mo agoI don't know about what other strictness you're referring to but exhaustive enum matching is common check in most TS stacks via eslint. Yea, it's not builtin, just saying there's a solution and it's super common.
- cyberax 8mo agoYou can actually have it built-in (via default case in 'switch' statements having a 'never()' statement). But it's less powerful than Rust's.
- nikeee 8mo agoOr you don't use the defualt case and rely on definite assignment analysis or checks for returns in every code path. I find the never type in TS actually being a proper bottom type + having control-flow based types vastly superior to what rust offers.
- tcfhgj 8mo agolast time I researched enums in TS for a project, they were a mess such that it was better not to use enums in the first place
- rtpg 8mo agoThe thing you gotta make sure to do is basically return inside of switch statements. Typescript will gladly propagate a type that you think is never but is actually ThatOneCaseYouForgot if it's not ever used or referred to. Every TS project I've worked on has an assertNever(val) thing specifically to check for this kinda stuff
- ceteia 8mo agoEnum matching is one of the better aspects of Rust.