Closed mihails-strasuns-sociomantic closed 6 years ago
(the problem is that you need to differentiate between TypeInfo.init
- the property of the TypeInfo
type itself and the initializer for the given user type represented by the particular TypeInfo
instance).
In one of our apps there was about a dozen of places where initializer was used - I fired this PR after having to version them all out to test with more recent compiler :)
how didn't we hit it before
It only got deprecated in 2.074 or something like that
Updated: clean up legacy double object.di situation
Missing release notes.
Updated to make it a new alias instead of deprecating new field. Looks like there is some relation between dmd1 and tangort about naming expectation so when I changed old fields, tests started to fail with wrong initializers.
This is simpler and will also do fine for our need.
Are you sure it is OK?
Yes (both because it is how it is done in druntime now and because of checking compiler :)).
Do we want to do this now that tango RT will be abandoned soon?
Not sure. It is rather annoying thing to version out for DMD 2.074+ but we can live without it. Change itself is also pretty simple though.
Ping @leandro-lucarella-sociomantic
Ping @leandro-lucarella-sociomantic
Can I try as well? Okay, here we go!
Ping @leandro-lucarella-sociomantic
I hope we don't regret it...
Matches change in D2 runtime intended to avoid confusion with built-in
T.init