dougdew64

@vmanot my goal when asking about errors when changing the dialect setting to C++17 wasn't to solve any of these problems. Rather, it was to generate compilation failures during the...

@vmanot I was about to perform the build setting experiment which I suggested earlier so that I could identify usages of C++20 features, but noticed that the build setting for...

@awni does your statement about active work on a swift front end mean that there's an effort happening somewhere that is not visible in this repo but will eventually be...

@awni Although I'm grateful that there will be a swift front end, I hope that performance of the c++ code will not be significantly compromised by the introduction of that...

Also, it seems that it's not possible to progress to the second test when the first test fails. Instead, every time that I press the Continue button, Xcode simply reports...

The exception is being thrown by the debug MTL gpu device. I'd assume that the debug device would perform stricter error checking than the release device. Is it possible that...

If I filter the tests to run only the argmin and argmax edge case tests which are in arg_reduce_tests.cpp, then I experience the same error which I had reported in...

Debugging a bit more, it seems that the logic in primitives.cpp is requesting that MTL set a zero-length buffer: 

Although the MTL docs don't say so, I'm guessing that the debug MTL device performs extra validation which decides to not create a buffer when the request is for a...

My hunch about this being a difference in the verification performed by different MTL devices (debug versus release) seems to be wrong. That `shape` buffer is not an unused buffer...