language_fan wrote: > The only problem with these was that there was no way to signal the > location of the type error in the client code, it always reported the > location of the (static) assert in the library, which is pretty much > useless.
That's a compiler problem, no? I don't think this is a big deal either way. Unit errors should be exceedingly rare. The purpose of a unit library not to track down unit errors, but to formally prove that correct code is correct. -- Rainer Deyke - rain...@eldwood.com
