Don <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #14 from Don <> 2012-07-25 01:21:56 PDT ---
(In reply to comment #13)
> I definitely think that we need to be able to get at the init values of
> Voldemort types. Too much generic code needs init for it to make sense to do
> otherwise. Not to mention, init is normally a public property, and you can 
> call
> public functions on Voldemort types just fine (e.g. front, popFront, etc.). If
> the creator of the Voldemort type really wants to make it so that you can't 
> use
> its init value, then they can @disable it.

But it requires the frame pointer of the function where it was defined. I think
it's an impossible request.

Voldemort types cannot merely not be named outside their enclosing function,
they cannot be created. It's not just a namespace privacy.
If you are using one, you are saying that .init does not exist for that type.

I think in this case it is wrong library design -- they shouldn't be used here.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to