Unclaimed project
Are you a maintainer of cppfront? Claim this project to take control of your public changelog and roadmap.
For a local variable whose name starts with "guard" we do not automatically move from last use. This gives language meaning to a naming convention of "guard" as a name prefix for guard-like stack objects, such as local std::scoped_lock objects, whose destructors are always the object's real last use.
With the changes below, notably to make the remaining tweaks for function syntax, I think version 0.8 is now stable enough to be ready for a license that allows commercial use. Thank you again to everyone who provided feedback and PRs so far!
Note: This project is still 'without warranty / use at your own risk' and cl...
isThanks to @filipsajdak for this PR! The built-in is implementation is now constexpr, and cases that are known statically now produce compile-time values.
using syntaxI had been using the Cpp1 syntax since I had nothing substantially better. But that did leave the grammar divergence between the two forms:
`...
Note: The first two were actually in 0.7.2 but I forgot to mention them in the 0.7.2 release notes.
is constraints on wildcarded parameters and locals.The following now works (and the last line would be an error if not commented out):
print: (r: _ is std::regular) = {
std::cout << "satisfies std::regular\n";
}
print: (_) = {...
iter1 ... iter2 or 1 ..= 100 (see docs: ... and ..= range operators)@regex metafunction by @MaxSagebaum (docs in progress)std::function< (i: inout int) -> forward std::string > and pointers to functions...