search for: pr22612

...body as-is (for Expected<T> returns) or return llvm::Error::success() (for Error returns). Clients who are actually using the remote-JITing features will now be able to return any errors that they had previously been dropping or bailing out on. This change is being tracked by https://llvm.org/PR22612 . I've held off making these changes for a while, because I know there are a lot of out-of-tree JIT clients and I want to avoid breaking your code. I think this churn is worth the pain though - the resulting APIs will have less historical baggage, be more error-proof, and enable some new featu...

...cted<T> returns) or return llvm::Error::success() (for > Error returns). Clients who are actually using the remote-JITing > features will now be able to return any errors that they had > previously been dropping or bailing out on. This change is being > tracked by https://llvm.org/PR22612 . > > I've held off making these changes for a while, because I know there > are a lot of out-of-tree JIT clients and I want to avoid breaking your > code. I think this churn is worth the pain though - the resulting APIs > will have less historical baggage, be more error-proof, a...