Christopher Horobin

[Christopher Horobin @c_horobin]

@y_nk @tannerlinsley @schanuelmiller @tan_stack @vite_js Yes satisfies keeps the inference but there are also context sensitive functions like `beforeLoad` return is piped into the parameter of `loader` which complicates things and also means the options have to be in a specific order

[Christopher Horobin @c_horobin]

@tannerlinsley @y_nk @schanuelmiller @tan_stack @vite_js We cannot use explicit types for the whole route definition because it needs to be an inference site. You need to infer from the route definition options users put there. I also prefer explicit types being totally optional for users and not required

[Christopher Horobin @c_horobin]

@y_nk @tannerlinsley @b_dammylolah @tan_stack This is a context sensitive function so the inference only works in a route definition. Seperate components would need explicit typing

[Christopher Horobin @c_horobin]

@tannerlinsley @y_nk @b_dammylolah @tan_stack You would still want to use Route bindings though. `Route.useX` and others which are extremely useful

[Christopher Horobin @c_horobin]

@MrPotatoDip The array variant is a fun use of homomorphic mapped types

[Christopher Horobin @c_horobin]

@eliseumds @tannerlinsley @letstri @tan_stack Parsing string literal can be quick and not really a concern here. The challenge with route definitions is they infer from validators and return types. Using a schema validator with good TS perf helps a lot

[Christopher Horobin @c_horobin]

@eliseumds @tannerlinsley @letstri @tan_stack We basically generate a route tree which is easy for TypeScript to consume but nothing in the route definitions is precompiled. The point is that what you write is fully inferred. The route tree generation sprinkles explicit types to link routes together

[Christopher Horobin @c_horobin]

@eliseumds @tannerlinsley @letstri @tan_stack Just to clarify. This is not precompilation. The route tree generation just ties the routes together, the rest is inference.

[Christopher Horobin @c_horobin]

@schanuelmiller @tannerlinsley `checkpoint` is like its way past my bedtime and really need to sleep and cannot put into words what I just did

[Christopher Horobin @c_horobin]

@colinhacks @schanuelmiller @tan_stack We have a fast path for empty objects because ` & {}` has a cost. Which for route parent merging happens in TSR. Might not for other libraries

[Christopher Horobin @c_horobin]

@seancassiere @tannerlinsley @lukerramsden Type level stuff is fun. The context switching between runtime and types can be challenging

[Christopher Horobin @c_horobin]

Never thought I would see the day this type checks in less than a second 🤯

[Manuel Schiller @schanuelmiller]

Always bet on TypeScript! Just ran a perf check on the Go implementation in a massive @tan_stack Router project.

Even without JSX (not supported yet), it’s already 3.3× faster than TS 5.8. Promising results! 🚀

[Christopher Horobin @c_horobin]

@GroveEsten @schanuelmiller @stevebeauge @someguys2nd @GabrielVergnaud Its likely not a bottleneck. It is best to trace before jumping to any conclusions. General advice like this can be useful but might not solve anything if the problem is something else

[Christopher Horobin @c_horobin]

@schanuelmiller @stevebeauge @someguys2nd @GabrielVergnaud There are different considerations with larger types and it comes down to how the types are used but this example is quite small, its not going to be slow either way

[Christopher Horobin @c_horobin]

@codewithdavid Don't actually use prisma. I'm always scared to touch any orm.

[Christopher Horobin @c_horobin]

Never thought I would be described in this way. Genius I'd reserve for him. I just like types.

[Tanner Linsley @tannerlinsley]

@AdamRackis @c_horobin He’s a genius. I may have designed a lot of the initial architecture, but he’s the one making things crazy fast and bulletproof. I am now the student of my own library.

[Christopher Horobin @c_horobin]

@schanuelmiller @mattpocockuk You mean this? https://t.co/86UZAGGLXI

[Christopher Horobin @c_horobin]

Type level code is just another language to learn. If you're uncomfortable looking at it, you probably don't know it that well

[Christopher Horobin @c_horobin]

It's like stale vs fresh

[Christopher Horobin @c_horobin]

Inference still happens, even during generation. You still wait for it.