digitalmars.D.bugs - [Issue 11041] New: Some function in core.stdc should be CTFEable
- d-bugmail puremagic.com (22/22) Sep 14 2013 http://d.puremagic.com/issues/show_bug.cgi?id=11041
- d-bugmail puremagic.com (13/20) Sep 15 2013 http://d.puremagic.com/issues/show_bug.cgi?id=11041
- d-bugmail puremagic.com (9/9) Sep 17 2013 http://d.puremagic.com/issues/show_bug.cgi?id=11041
http://d.puremagic.com/issues/show_bug.cgi?id=11041 Summary: Some function in core.stdc should be CTFEable Product: D Version: D2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: druntime AssignedTo: nobody puremagic.com ReportedBy: ttanjo gmail.com It prevents some functions in Phobos from being CTFEable. For instance, core.stdc.string.memcpy prevents std.algorithm.move from being CTFEable (I think it should be). A workaround for it is that we implement functions in druntime in D by ourselves in each module but it is better to provide their CTFEable implementations in druntime. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Sep 14 2013
http://d.puremagic.com/issues/show_bug.cgi?id=11041 bearophile_hugs eml.cc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bearophile_hugs eml.ccIt prevents some functions in Phobos from being CTFEable. For instance, core.stdc.string.memcpy prevents std.algorithm.move from being CTFEable (I think it should be). A workaround for it is that we implement functions in druntime in D by ourselves in each module but it is better to provide their CTFEable implementations in druntime.One possible solution is to never use core.stdc.string.memcpy directly in Phobos, and define a D wrapper that contains __ctfe and calls core.stdc.string.memcpy if that's false. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Sep 15 2013
http://d.puremagic.com/issues/show_bug.cgi?id=11041 The initial bug report is too vague. We need a list of functions. Is it just memcpy() and memmove() ? Or are there others? We also need to consider if the use of those functions in making those algorithms un safe. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Sep 17 2013