Foo / Foo.ref is a backward default; should be Foo.val / Foo

[Dan Smith]

On Apr 26, 2022, at 8:45 AM, Kevin Bourrillion <kevinb at google.com<mailto:kevinb at google.com>> wrote:

I think I would insist that `.val` be spelled with only one additional character... or even that the value type be generated as the snake_case form of the name!

Okay, this is a meaningful refinement that I find less objectionable.

If it's '#Integer128' or 'Integer128!' instead of 'Integer128.val', we've trimmed away a chunk of the typing/reading overhead (though it's still there, and I think some of the overhead is directly in service of what you find attractive—the idea that the value type is something unnatural/a departure from the norm).

If it's 'integer128' and 'Integer128', well now there is no "default" type, and I think we're talking about something categorically different. There are some new (surmountable?) problems, but my earlier objections don't apply.