Builtin get and set operations cannot be shadowed when using dot notation

[IR0NSIGHT]

linter bug: Unbox requires a boxed type, but got Array[Int].effekt
minified example:

def test(arr: Array[Int]) = {
	arr.put(3,12)
}

[jiribenes]

Hi @IR0NSIGHT,

thanks for reporting.
If you want a temporary workaround, just use put(arr, 3, 12) instead :)

I'm running into the same problem in Advent of Code. I can also trigger the error message when using get. I think the culprit is the get and put builtins which [somehow] take precedence over user-defined functions when used with dot-syntax.

Here's the definition of get and set (originating from TState above)

effekt/effekt/shared/src/main/scala/effekt/symbols/builtins.scala

Lines 85 to 86 in 4d2e486

	"get" -> TState.get,
	"put" -> TState.put

[jiribenes]

Simple reproduction which doesn't need the import of mutable/array:

def get(x: Int): Int = x + 42

def main() = {
    val result = 100.get
    println(result)
}

produces the error:

[error] issue.effekt:4:18: Unbox requires a boxed type, but got Int.
    val result = 100.get
                 ^^^

which originates in Typer:

effekt/effekt/shared/src/main/scala/effekt/Typer.scala

Line 450 in 4d2e486

Context.abort(pretty"Unbox requires a boxed type, but got $vtpe.")

However, calling get as a function directly (without dot notation) works:

def get(x: Int): Int = x + 42

def main() = {
    val result = get(100)
    println(result) // prints 142
}

[jiribenes]

Is this requirement still necessary with #305, @b-studios? It would be nice to "release" get and put to be overloaded by the users.