char[]/ubyte[] compile error

Jacob Carlborg via digitalmars-d-ldc digitalmars-d-ldc at
Thu Jul 13 23:15:19 PDT 2017

On 2017-07-14 00:06, Johan Engelen wrote:

> What I mean is, a construct like your "Array" on the D-side, that is 
> automatically convertable from/to a slice on the D-side. Such that you 
> can define cross-C++-D functions that accept slices on the D-side, and 
> accepts Array structs on the C++ side, and all is mangled properly 
> because the D-side is also using the Array struct yet still accepting 
> slices.

Yeah, that would be nice. This feature request is related [1]. If that's 
implemented and we're satisfied without any implicit conversions we 
would not need any special language support. The feature request is 
useful for other scenarios as well.


/Jacob Carlborg

More information about the digitalmars-d-ldc mailing list