4 ms·
Because once you ship it without definition checking, three years later it's too late to add it. Too many people will have written code that will break. This
by marvy 11y ago
Because once you ship it without definition checking, three years later it's too late to add it. Too many people will have written code that will break. This is one of those unfortunate language features that you only get one chance to get it right. Note: I haven't been following this stuff closely, I could be missing something here, but I trust that someone will correct me if I'm wrong. Or at least down-vote me to oblivion :)
- Rexxar 11y agoThe current specification create a "concept" keyword. Why the fully checked concepts couldn't just use another keyword like "checked_concept" that behave exactly like the "concept" keyword for user of the library ? Library implementers can then migrate progressively their code when they can. edit: or, alternatively, create a "checked_template" keyword when implementing a checked template.
- moomin 11y agoIn any event, it looks like concepts have indeed been kicked to the kerb. I think the definition checking was important, and some were concerned that there was no library implementation using it, which means they haven't shaken it out in practice yet.
- moomin 11y agoIn any event, it looks like concepts have indeed been kicked to the kerb. I think the definition checking was important, and some were concerned that there was no library implementation using it, which means they haven't shaken it out in practice yet.