mw66

And for the current `sliced` behavior (i.e only take partial array as converted N-d array from the head of the input array): the user can always do it *explicitly* via...

> should be fixed in `v3.10` Excellent. Thanks.

I'm patient :-)

I saw this new user's mistake: https://forum.dlang.org/post/[email protected] i.e. sliced -> fuse Since there will be a new breaking (or deprecation) change release, I'd want to suggest we should deprecate both...

> should be fixed in `v3.10` It's v3.14.14 now :-) or it's done already?

BTW, in Ubuntu, you can setup the ta-lib by: ``` sudo apt install linuxbrew-wrapper brew install ta-lib ```

I've thought the problem is not about mangled names, but about: ``` %talib._IO_FILE* v.s. %core.stdc.stdio._IO_FILE* ``` and in https://github.com/ldc-developers/ldc/issues/2782#issuecomment-495171179 ``` %libxlsxd.xlsxwrap._IO_FILE* v.s. %core.stdc.stdio._IO_FILE* ``` i.e. the _IO_FILE become a symbol...

My manually modified generated file is here: https://github.com/mingwugmail/talibd/blob/master/source/talib.d#L67 ``` public import core.stdc.stdio; ... version (DigitalMars) { struct _IO_FILE {...} } ``` I think this is the only modification needed for...

I can find the news, but not the dev files: https://streamhpc.com/blog/2017-02-22/nvidia-enables-opencl-2-0-beta-support/

is it this one ? https://github.com/NVIDIA/nvidia-docker/issues/17 We just published the OpenCL images on DockerHub (finally!). https://hub.docker.com/r/nvidia/opencl/ looks like it is defined: root@91dbfd615000:~# grep CL_VERSION_ /usr/include/CL/* | grep -w define /usr/include/CL/cl.h:#define...