search for: alexandrescu

> I like this idea in general. It's a better implementation of what > ErrorOr originally was before we removed the custom error support > because it wasn't used. In fact I would actually support outright > replacing ErrorOr with this if it can be done safely, as I find the > name TypedErrorOr a bit long. The main differences are * This will hopefully be used. *

...The situation before was >> not that ErrorOr was std::error_code or T. >> >> Since we are adding it, I would also support replacing every use of >> ErrorOr with TypedErrorOr and renaming it. >> > > Alternative name could be Expected<T> as proposed by Andrei Alexandrescu. > > >> >> Cheers, >> Rafael >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > > _______________________________...

I've been trying to come up with some good coding standards, but I've realized that most of us already know most of this. So instead of trying to define every aspect of how we code Compiz-code, I'll try to outline some of the finer points. For a more complete list, you can review any of the many coding-standard documents out there (For Linux, FreeBSD or any other project). Part of