I'm a very proud daddy and a freelance C++ programmer (server side on Windows, Linux and Mac). I cook, ski, run and dabbled in robotics & embedded assembly.
This project cannot build given the current state of the project...
Go on Visual Studio, tell me what the problem is...
This project cannot build given the current state of the project. - Rambling Comments - Len Holgate's blog
@olson_dan I spent some time with Rust will spend more, but I find it harder to "sketch" code in Rust than in C++. This is possibly the point and may prevent code that allows bad usage from existing at all... But it slows me down at present. And, it's just enforcing ref counts and locking;)
The Visual Studio bug is now fixed and awaiting a release.
https://developercommunity....
A hacky workaround is to rename VSFileHandler.dll and VSFileHandler_64.dll
The bug manifests in ANY dialogs that use explorer to render directory lists...
If anyone else is experiencing "random" Windows Explorer crashes/restarts when browsing to directories containing Visual Studio solution files then it may be that the .sln files have unix line ends and (all of a sudden it seems) that's bad - https://t.co/lH94WOuGjN
If anyone else is experiencing "random" Windows Explorer crashes/restarts when browsing to directories containing Visual Studio solution files then it may be that the .sln files have unix line ends and (all of a sudden it seems) that's bad - https://t.co/lH94WOuGjN
Half my career is me writing up how to do something and then 10 years later googling for it cause I forgot and discovering that I alone had that problem.
Anyone knows faster (non-syscall) way to do following, without building a table?
USHORT GetCurrentProcessorNumaNode () {
PROCESSOR_NUMBER processor;
GetCurrentProcessorNumberEx (&processor);
USHORT numa;
GetNumaProcessorNodeEx (&processor, &numa);
return numa;
}