Displaying value information in an IDE is tricky.
For union types, it's more helpful to see the inferred type (Option<Player> versus null). For product types it's often nicer to see an example value.
For primitive types I almost always want a value (0 versus int).
miniblog.
Related Posts
Amazon is using LLMs to summarise product reviews!
Seems like a great application of the tool, but I haven't seen many deployments of AI summaries in the wild yet.
Displaying value information in an IDE is tricky.
For union types, it's more helpful to see the inferred type (Option<Player> versus null). For product types it's often nicer to see an example value.
For primitive types I almost always want a value (0 versus int).
Shower thought: Printing runtime values is far more useful for product types than sum types.
For a struct it's useful to see all the fields, but for a nullable int it's less useful to see 123.
