@simoncropp Only if there was a VB-esque concept in the language itself as the types being automatically convertible.
Honestly, I doubt it.
1
Discussion
Loading...
@jeremydmiller i am curious. link?
1
@simoncropp https://github.com/JasperFx/wolverine/issues/2465
The problem is that they're neither fish, nor fowl, and you almost always have to treat them specially by either unwrapping or wrapping the real value
1
@jeremydmiller would it be easier if strong typed ids were a first class feature in .net?
1
@simoncropp Only if there was a VB-esque concept in the language itself as the types being automatically convertible.
Honestly, I doubt it.
1
@[email protected] @[email protected] I'm not a fan in general for a lot of other reasons, but the fact that TypeScript types only exist at compile time (and you can tell the compiler to ignore them) does make things like strongly typed IDs easier to deal with. Generated code can just throw the types away, while user facing code gets type safety (for the value of safety TS allows at the best of times) on ID types without run time impact. Haskell allows alias types that have similar properties.
It's not really the kind of thing the dotnet type system is set up to deal with gracefully though.
1
@[email protected] @[email protected] Case in point: I use strong IDs in my TypeScript and Haskell projects, but I don't in my F# project that uses Marten. And it isn't because of Marten's support for them or not; it's the amount of hassle it causes in other places and the annoying nagging feeling of taking a run time overhead for code that is less pleasant to work with.
bonfire.mavnn.eu
News and community around mavnn.eu projects.
Automatic federation enabled