What would the advantage be to that over the programmer putting in a try/catch
into the @compile_workload
block? In general I’m a little reluctant to hide errors unless there’s a really good reason to do so. For example, open(f, filename)
definitely needs a try catch around f
in order to satisfy its promise to close the file after calling f
, but there’s no guarantee I know of that precompilation should succeed even for buggy workloads. (I’m sure you know that’s not an accusation about the quality of your LanguageServer workload. If I had a nickle for every buggy workload I’ve written…)
If try/catch
is needed, I’d rather it be explicit in the code that everyone can see when inspecting the package.