map access `or` block behavior is inconsistent with the rest of the language about v

[shove70]

No, it's not about V.

fn get_value(m map[string]int, key string) ?int {
	return m[key] or { none }  // The or block here is map specific and is where we handle when the key doesn't exist
	                           // The priority of this or block is to the map, not to the previous return
}

fn even_or_none(i int) ?int {
	return if i % 2 == 0 { i } else { none }
}

fn useless_fn(i int) ?int {
	return even_or_none(i) or { none } // The or block here is the option that handles the return value of fn even_or_none()
}

They're not the same

[shove70]

fn get_value(m map[string]int, key string) ?int {
	return m[key] or { return none }
}

So it works

[juan-db]

Result behaves the same as Option.

fn even_or_error(i int) !int {
	return if i % 2 == 0 { i } else { error('${i}') }
}

fn useless_fn(i int) ?int {
	return even_or_error(i) or { none }
}

I can't think of another example that uses or syntax. So why should map behave differently from Result and Option?