http://d.puremagic.com/issues/show_bug.cgi?id=9102
--- Comment #7 from Johannes Pfau <[email protected]> 2013-02-25 10:57:57 PST --- You're probably right with most of that. I'd still like to keep the name as "put" to avoid API breakage and for consistency with the OOP API. Also introducing a special reference type complicates the API, if we keep "put" the pointer type can be used as that reference type. Disabling the postblit on CRC32 is IMHO a quite nice solution. It should be done anyway as in 99% if a CRC32 is passed to another function by value it's a bug and a @disabled postblit would prevent this nicely. It should therefore also prevent calling copy with a CRC32. The only place where @disabling postblit should produce a different result than renaming "put" should be if a function takes an OutputRange by ref, such as the standalone put function. But I don't think that's a problem. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
