https://d.puremagic.com/issues/show_bug.cgi?id=9633
Vladimir Panteleev <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Vladimir Panteleev <[email protected]> 2014-03-02 18:06:33 EET --- Why is it a requirement that F() should not compile? I have filed issue 12230 which is an opposite of this pull request. Some things to be aware of: - Inside speculative blocks (in __traits(compiles) or typeof(exp)), we always pretend that we have an "is" pointer. This greatly simplifies writing template constraints for methods, among other things. - The rules for fields and methods differ when they are passed as alias parameters (see issue 12230). When a field is passed as an alias parameter, the template becomes nested within the field's aggregate (struct/class). When a method is passed, this doesn't happen, which I think is an unwarranted inconsistence. -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
