mw66

btw, it's defined in another included file: /usr/include/driver_types.h ``` typedef __device_builtin__ enum cudaError cudaError_t; ```

Found work-around: let `dstep` work on the `cpp` preprocessed output `.i` file: ``` $ gcc -E /usr/include/cuda_runtime_api.h > cuda_runtime_api.i $ dstep ./cuda_runtime_api.i -o cuda_runtime_api.d ``` Maybe you can add this...

> Please include the input and the expected output. $ dpkg -S /usr/include/cuda_runtime_api.h nvidia-cuda-dev:amd64: /usr/include/cuda_runtime_api.h $ wc /usr/include/cuda_runtime_api.h 12077 67841 509599 /usr/include/cuda_runtime_api.h $ dpkg -l nvidia-cuda-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/...

@jblachly you can try my workaround: feed `cpp` generated single .i file to dstep https://github.com/jacob-carlborg/dstep/issues/280#issuecomment-1148065013

Same issue on a new machine: ``` $ dub run dstep Building package dstep in /home/xxx/.dub/packages/dstep-1.0.3/dstep/ ## Warning for package dstep, configuration test-functional ## The following compiler flags have been...

@baryluk maybe you want create a PR? Just-Do-It :-)

Please make a release with these changes +1

OK, I have showed my point theoretically (in the OP). Now I just did the following test, it shows (actually proves) The MFI function has *no* unstable period (up to...

Well, I think the upstream in the ta-lib.org is dead. The last code update on source forge https://sourceforge.net/p/ta-lib/code/HEAD/tree/trunk/ta-lib/ Is in 2013. Do you know it's still under maintenance?

Oh, the new one is here: https://github.com/TA-Lib/ta-lib but it says it's "unofficial"?