No need to put \rho to the object after taking \lambda

[maxonfjvipon]

Here we're trying to copy and put \rho to the object that we get after executing \lambda. I suggest not to do this because:

1. all of the objects returned from \lambda already have bound \rho attribute
2. even if just anonymous abstract object is returned from \lambda - there's no sense to bind its \rho with original atom. It'll just add more unnecessary complexity and confusion.
3. it'll let us not to create a dozens of unnecessary objects in runtime

@yegor256 WDYT?

[yegor256]

there's no sense to bind its \rho with original atom

@maxonfjvipon why so?

[maxonfjvipon]

@maxonfjvipon I think \rho should refer to the parent object. If object has a parent - it means that parent has an attribute which bound with current abstract object, but \lambda is an asset but not attribute and atom don't have don't have any more attributes (except void ones but they don't require \lambda to execute).

[yegor256]

@maxonfjvipon ok, make sense