A platform is a function of it's moderation, and I do not wish to participate in the platform that twitter is going to be just like I don't want to participate in sites like 4chan or kiwifarms. I'm sorry to those that disagree, but those are my reasons.
@ericniebler@pdimov2@seanbax@odinthenerd About that... for metacheck I might actually want to create a list of all possible test cases which would probably involve some sort of cartesian product + transform + unique, which could easily be over 10k elems. That's essentially the reason I haven't done that so far.
@odinthenerd @dascandy42 Either way it's four specializations, but one is a single memoized lookup and alias call more. Besides that, volatile is only ever used in tests anyway so combined is definitely faster.
@Guriwesu @Sickeroni That's true, but if you don't inherit from the iterator you have to conditionally implement all the operations depending on the original iterator type using SFINAE. I'd wager that implementing a full version of the indexed wrapper would be several hundered lines of code that way.
for (auto [i, v] : indexed{arr}) {
https://t.co/hP7PT2oeMY
So this works, except standard iterators are inconsistent, so it doesn't.
Props to @Sickeroni for the inspiration.
@Manu343726 Probably because it wasn't very practically usable before this, it'd take about 8Gb of RAM to compile the complete kvasir::mpl test suite. Right now it's down to about .5Gb or so, not sure.
Leaving @emBOconference at last, lots of interesting talks about resource constrained code and zero cost abstractions, i appreciate the clear vision on modern c++ design there was throughout all of the conference.
@JasonRice_@odinthenerd The documentation can be made by building the standardese cmake target, it might be a good idea to put those files online somewhere.
@EscJaeger@odinthenerd We haven't put out a release yet as we want to freeze the public interface first, so the master branch is still an early/concept version.