[Issue 1985] import expression should return ubyte[] not string

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=1985

--- Comment #20 from ag0aep6g <ag0aep6g at gmail.com> ---
(In reply to RazvanN from comment #18)
> (In reply to ag0aep6g from comment #17)
[...]
> > Age ("it's been that way for years") is not a reason to not fix an issue.
> > 
> 
> This is not a bug, as the spec is perfectly clear on what an import
> expression returns [1]. It is at most an enhancement report.

I didn't write "bug", I wrote "issue". This issue is categorized as a bug,
though. You didn't change that.

[...]
> Adding a fix for this in the compiler is a trivial task. That is not the
> point here, but rather not to change something that has low impact, has
> library alternatives and might be used by people as is.

There is a difference between prioritizing high impact changes and outright
refusing to do or even accept low impact changes. The former is fine. The
latter is declaring bankruptcy.

[...]
> > I can't say I like it, but it looks like a workable compromise.
> > Special-casing `cast(...) import(...)` in the spec could also work.
> 
> The spec is perfectly clear that a string literal is returned.

Yeah, we all know that. But a way to get something else would be nice.

--