[mccanne]

No description provided.

[philrz]

Suggested change

	is an `int64` where it's present and absent elsewhere.
	is an `int64` in the values that include the field and absent from the rest.

I paused for a long time on "present". I'm not sure if my suggested alternative is correct/clearer, though.

[philrz]

Suggested change

	it's kept like any other value.
	it isn't dropped from records, arrays, or the output of `values`.

My Claude paused here because "kept like any other value" could be read as saying none of the "handled quietly" rules above apply to an option-type none. But it still shares some of those behaviors with plain none, as summarized below, hence the narrower wording.

"Handled quietly" rule for plain none	Applies to none::int64?
dropped from values output	no: none::int64 is output
disappears from records, arrays	no: {a?:none::int64}, [1,none::int64]
aggregates skip it	mixed: sum(this) skips it, collect(this) keeps it ([1,none::int64])
?? replaces it	yes: 5
?. passes it through	yes

[philrz]

Suggested change

	one type, e.g., in a record type formed by
	[type fusion](../super-sql/type-fusion.md), the value of
	a field that is absent from the original record.
	one type, e.g., a field of a record type formed by
	[type fusion](../super-sql/type-fusion.md) that is absent from some of the original records.

[philrz]

Suggested change

	# spq
	values {a:1},{b:2} | values a.ok(), a.ok() ?? 0
	# input
	# expected output
	1
	1
	0
	# spq
	values {a:1},{b:2} | values {input:this, ok:a.ok(), with_default:a.ok() ?? 0}
	# input
	# expected output
	{input:{a:1},ok:1,with_default:1}
	{input:{b:2},with_default:0}

I paused a bit at the combination of 2 inputs + 2 values args but only three output values. I think this way may more clearly show where the none is being dropped.