Simpler take on builder pattern and context functions

[AMatveev]

It is not a new discussion. Here is my latest totals: Literal Abstractions - #7 by AMatveev
Also,I can say I do not understand statements which say that there are no problems it is ok and scala has all it needs.

I think the main power of OOP is the scope management:

What can make scala more popular?

On the subject of what makes a language popular this is a pretty interesting talk: https://youtu.be/QyJZzq0v7Z4

And currently the only way to compose scopes is to create object and classes:

DelayedInit or OnCreate, any solution?

Some sort of DelayedInit replacement for scope management: import db.Connection @main def main():Unit = { val c = new Connection() //It is less error prone because nobody can forget to call method and do import. //And it is more easy to write c.execute{new{ setValue(2.ss) }} } package db class Statement(){ var value:String = "default value" def execute():Unit = println(s"value=$value") } class StatementBuilder(given private val s:Statement){ //here it can be extensions…

Is the anonymous object is the right choose for scope management. It seems the less evil in some cases for me.
So it is quite difficult choice for me whether I should:

• Use imports

  It leads to boilerplate code

• Use global imports

  It has low coupling

• Use inheritance

  It is quite heavy

I think existence of such choice it is quite bad by itself. And It indicates that the task has no good decision.