Barry Bond
F# 4.0 depends on msbuild 14, which also isn't installed (error FS0193: Could not load file or assembly 'Microsoft.Build.Utilities.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot...
The logic in the ./everest script, for setting VS_BIN, doesn't work for VS2017. They refactored out the tools from the IDE, with new directory structures. - VCToolsInstallDir points to a...
I haven't tried Vale using F# 4.1. The 2015 tools are in a different directory structure than they were in the original VS 2015 install... the assembler is now in...
I can't think of a reason why we would want to use the 2015 toolchain. If we stick to 2017, we avoid the hassle of having to dual-target for the...
Caroline, Vale, the one user of scons in our build at present, is already building with Scons 3 and Python 3. Awkwardly, the build machine may still be using Scons...
Is this still an issue? If so, it probably makes sense to move into the F* issue tracker, and be prioritized appropriately.
I think this problem is that the effect declared is EXT, but the actual implementation has ML effect (it can throw). I hit this long ago, when I was writing...
Can you follow up on this, to make sure it is addressed during verification? If it is truly a bug in the TLS 1.3 codepath.
Assigning to you, to determine if this is a bug, and if it'll be caught/fixed during verification work.
Assigning to you. Can you please check if this is still a bug? And if so, it should be caught and fixed during the verification push.