Literal Abstractions

[AMatveev]

@YourPsychiatrist

defineProperty { (leftOp: Int, rightOp: Int, theResult: Int) =>
    if leftOp != 0 && rightOp != 0 then theResult != 0 else itDoesntHold
} of multiply

if I understand your example correctly, there is similar proposal:

PRE SIP: ThisFunction | scope injection (similar to kotlin receiver function)

name of feature this functions, dsl function, context functions, receiver function or import function don’t know which name is better. In whole document i’m using this function consequently. specification I propose to introduce additional trait into scala trait ThisFunction[-T, +R] extends Function1[T, R] //trait ReceiverFunction[-T, +R] extends Function1[T, R] //trait ContextFunction[-T, +R] extends Function1[T, R] //trait ImportFunction[-T, +R] extends Function1[T, R] //trait DslFunction[…

The main drawback of such aproach is:

@morgen-peschke

While they assert this, I don’t know if I buy that. Having to look up the function definition to figure out what was in scope was really annoying, back when I programmed in Perl.

The it version is less bad, as at least there’s something for the autocomplete to key off, but the this version dumps stuff into the current namespace, without a clear way to figure out what’ in scope.

Dotty allows to implement “it pattern”.

Nevertheless I am sure that such such ability is very important for dsl especially for typeclasses because an extension has no sence with “it” prefix.

There are also many use cases for this feature.

@kai

I want scope injection for ZIO Test’s immutable builder – right now all tests written with it must include boilerplate imports: