search for: jiterror

...scribe what went wrong. There's no practical way to maintain a serialization routine for all possible std::error_codes that might come up, even if they were powerful enough to describe everything that could go wrong (which again, being static kinds, they're not). With my proposal however, a JITError base class can be defined as: class JITError : public TypedErrorInfo<JITError> { public: virtual void serialize(RPCChannel &C) const = 0; }; Now you just describe serialization/deserialization for each error when you define it. :) (Yes - this hand waves over deserialization. It's...

...re's no practical way to maintain a serialization routine for >> all possible std::error_codes that might come up, even if they were powerful >> enough to describe everything that could go wrong (which again, being static >> kinds, they're not). With my proposal however, a JITError base class can be >> defined as: >> >> class JITError : public TypedErrorInfo<JITError> { >> public: >> virtual void serialize(RPCChannel &C) const = 0; >> }; > > What prevents you from using a diag handler in the jit server that > sends err...

...routine >> for >> >> all possible std::error_codes that might come up, even if they were >> powerful >> >> enough to describe everything that could go wrong (which again, being >> static >> >> kinds, they're not). With my proposal however, a JITError base class can >> be >> >> defined as: >> >> >> class JITError : public TypedErrorInfo<JITError> { >> >> public: >> >> virtual void serialize(RPCChannel &C) const = 0; >> >> }; >> >> >> >> Wha...

> > I don't think these are really independent. Whether or not you need to emit > > a diagnostic depends on whether a caller can handle the corresponding error, > > which isn't something you know at the point where the error is raised. > But you do in the diag handler. For example, if you are trying to open > multiple files, some of which are bitcode, you know to