[Issue 17390] Pass flags to linker driver without -Xlinker

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #4 from Timothee Cour  ---
also, -Xcc is now part of ldc

--

[Issue 17390] Pass flags to linker driver without -Xlinker

[d-bugmail--- via Digitalmars-d-bugs]

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

Timothee Cour  changed:

   What|Removed |Added

 CC||timothee.co...@gmail.com

--- Comment #3 from Timothee Cour  ---
ping on this.

this would enable:

* same motivations as https://github.com/ldc-developers/ldc/issues/2093
(Passing options directly to CC)


* makes it easier to switch back and forth between clang build command line and
D build command line, by prepending linker arguments with `-Xcc=`, eg:

```
dmd -Xcc=-Wl,-rpath,some_rpath,-lfoo,-Lbar
``

--

[Issue 18282] [Scope][DIP1000]Assignment of local variable to `scope` variable not recognized by compiler

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #4 from Walter Bright  ---
https://github.com/dlang/dmd/pull/8030

--

[Issue 18608] containers/src/containers/internal/storage_type.d(50)

[d-bugmail--- via Digitalmars-d-bugs]

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

Timothee Cour  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Timothee Cour  ---
moved to https://github.com/dlang-community/containers/issues/101

--

[Issue 18608] containers/src/containers/internal/storage_type.d(50)

[d-bugmail--- via Digitalmars-d-bugs]

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

Timothee Cour  changed:

   What|Removed |Added

 CC||timothee.co...@gmail.com
   Severity|enhancement |regression

--

[Issue 18608] New: containers/src/containers/internal/storage_type.d(50)

[d-bugmail--- via Digitalmars-d-bugs]

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

  Issue ID: 18608
   Summary: containers/src/containers/internal/storage_type.d(50)
   Product: D
   Version: D2
  Hardware: x86
OS: Mac OS X
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: phobos
  Assignee: nob...@puremagic.com
  Reporter: timothee.co...@gmail.com

getting these:

containers/src/containers/internal/storage_type.d(50): Deprecation: Symbol
`std.traits.isBasicType(T)` is not visible from module `storage_type` because
it is privately imported in module `typecons`


in CI:
https://circleci.com/gh/dlang/phobos/6521?utm_campaign=vcs-integration-link_medium=referral_source=github-build-link

of this:
https://github.com/dlang/phobos/pull/6178

--

[Issue 18585] Linker error if compiled with -dip1000

[d-bugmail--- via Digitalmars-d-bugs]

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

Carsten Blüggel  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
  Component|dmd |phobos
 Resolution|--- |FIXED

--- Comment #2 from Carsten Blüggel  ---
Fixed by
https://github.com/dlang/phobos/commit/92877fddb5fff7b76e95fd35fd50036cb57b9ba4

--

[Issue 18607] using labelled continue in tuple foreach can break pure and @safe

[d-bugmail--- via Digitalmars-d-bugs]

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

ag0aep6g  changed:

   What|Removed |Added

   Keywords||safe
 CC||ag0ae...@gmail.com
   Hardware|x86 |All
Summary|using labelled continue in  |using labelled continue in
   |tuple foreach can break |tuple foreach can break
   |pure|pure and @safe
 OS|Windows |All

--- Comment #1 from ag0aep6g  ---
When returning a pointer, this also breaks @safe:


int* test(T...)() @safe pure {
L:foreach(_; T) {
continue L;
return null;
}
}


--

[Issue 18535] auto-tester fails on Win_32_64 : `The system cannot find the path specified.`

[d-bugmail--- via Digitalmars-d-bugs]

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

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #2 from Seb  ---
See: https://github.com/braddr/d-tester/issues/71 for the underlying issue.

--

[Issue 18605] Missing return not detected when labeled continue is used

[d-bugmail--- via Digitalmars-d-bugs]

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

Yuxuan Shui  changed:

   What|Removed |Added

Summary|False unreachable warning   |Missing return not detected
   |generated when labeled  |when labeled continue is
   |continue is used|used

--

[Issue 18607] New: using labelled continue in tuple foreach can break pure

[d-bugmail--- via Digitalmars-d-bugs]

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

  Issue ID: 18607
   Summary: using labelled continue in tuple foreach can break
pure
   Product: D
   Version: D2
  Hardware: x86
OS: Windows
Status: NEW
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: elpenguin...@gmail.com

int test(T...)() pure {
L:foreach(_; T) {
continue L;
return 1;
}
}

The only return statement in this function is unreachable, so this returns an
uninitialized int as long as >= 1 template parameter is specified. This should
not have been able to be marked pure.

The pure attribute is automatically inferred but I've explicitly added it here.

--

[Issue 18417] Make const and immutable postblit constructors illegal

[d-bugmail--- via Digitalmars-d-bugs]

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

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com

--- Comment #5 from RazvanN  ---
(In reply to Steven Schveighoffer from comment #4)
> Posted it on the forums as well, but I'll do so here too:
> 
> postblit is what is used to do things like reference counting. You may be
> altering data that isn't actually part of the struct, so we still do need a
> postblit capability for immutable structs.
> 
> Basically the same thing that anonymous4 said, but with a real use case.
> 
> (In reply to Jonathan M Davis from comment #3)
> > And it's impossible for an immutable or const postblit
> > constructor to be called in the first place. If you try and declare a const
> > or immutable postblit constructor, you just end up with compilation errors,
> > because they don't work - and they can't work, not for what the purpose of a
> > postblit constructor is.
> 
> The purpose is to run some code after blitting. Which is perfectly
> reasonable for immutable and const structs as well.
> 
> What we should do is make it possible for immutable/const postblit to work.
> 
> i.e.
> 
> immutable S s;
> immutable y = s; // Error: immutable method S.__postblit is not callable
> using a mutable object
> 
> Why does it think y is mutable? This should work.

That's a different problem: the compiler creates a function __postblit which
represents the postblit; when it does that it checks for the struct declaration
qualifiers (in this case, none) and forwards them to the postblit. Later, when
the immutable instance is created, all members are considered immutable, except
for the postblit. That is also the case for shared : [1]

[1] https://issues.dlang.org/show_bug.cgi?id=18474

--

[Issue 18606] New: [REG2.072] "cannot append type const(T) to type T[]" in .dup

[d-bugmail--- via Digitalmars-d-bugs]

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

  Issue ID: 18606
   Summary: [REG2.072] "cannot append type const(T) to type T[]"
in .dup
   Product: D
   Version: D2
  Hardware: x86_64
OS: Linux
Status: NEW
  Keywords: rejects-valid
  Severity: regression
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: dlang-bugzi...@thecybershadow.net

/ test.d /
struct S
{
struct T
{
int foo;
int[] bar;
}

struct M()
{
T[] arr;

this(this)
{
arr = arr.dup;
}
}

M!() m;
}
//

Introduced in https://github.com/dlang/dmd/pull/5500

--

[Issue 18605] False unreachable warning generated when labeled continue is used

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #2 from Yuxuan Shui  ---
Reduced a bit more:

auto test(T...)() {
L:foreach(_; T) {
continue L;
return 1;
}
}

void main() @safe {
import std.stdio : writeln;
writeln(test!(1,2,3)());
}

--

[Issue 18605] False unreachable warning generated when labeled continue is used

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #1 from Yuxuan Shui  ---
This bug is worse than I thought:

auto test(T...)(int t) pure {
L:foreach(_; T) {
if (t)
continue L;
return 1;
}
}

void main() @safe {
import std.stdio : writeln;
writeln(test!(1,2,3)(1));
}

Results in an uninitialized return value in @safe code.

--

[Issue 12486] Function returning struct isn't called if `enum` of its result is accessed

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #4 from FeepingCreature  ---
Posted a pull request that's awaiting review:
https://github.com/dlang/dmd/pull/8013

I'm not really happy with it, but I don't know a better way to write it.

--

[Issue 18605] New: False unreachable warning generated when labeled continue is used

[d-bugmail--- via Digitalmars-d-bugs]

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

  Issue ID: 18605
   Summary: False unreachable warning generated when labeled
continue is used
   Product: D
   Version: D2
  Hardware: x86_64
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: yshu...@gmail.com

Code example:

auto test(T...)(int t) {
L:foreach(_; T) {
if (t)
continue L;
return 1;
}
new int; // <-- reported as unreachable
}

int _() {
return test!(1,2,3)(1);
}

While in reality the reachability of 'new int' is dependent on parameter 't'.

--

[Issue 7804] Cannot alias __traits directly

[d-bugmail--- via Digitalmars-d-bugs]

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

Basile B.  changed:

   What|Removed |Added

 CC||b2.t...@gmx.com

--- Comment #9 from Basile B.  ---
I've managed to get it working for types. It has to because the grammar has to
changed so that __trait(getMember,...) becomes a BasicType.
To be clear my hacked DMD for

  struct Foo{struct A{}}
  alias FooA = __traits(getMember, Foo, "A");
  pragma(msg, FooA.stringof);

says: "A". Or even

  struct Foo{alias MyInt = int;}
  alias FooInt = __traits(getMember, Foo, "MyInt");
  static immutable FooInt fi = 42;
  pragma(msg, fi);

says "42"

Next step is for variables and other symbols.
WIP here: https://github.com/BBasile/dmd/pull/1/files

--

[Issue 12597] Payload getter for std.typecons.Typedef

[d-bugmail--- via Digitalmars-d-bugs]

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

Bastiaan Veelo  changed:

   What|Removed |Added

 CC||basti...@veelo.net

--- Comment #16 from Bastiaan Veelo  ---
(In reply to bearophile_hugs from comment #15)
> (In reply to bearophile_hugs from comment #14)
> 
> > > auto typedefVal(T)(T val)
> > > {
> > > return cast(TypedefType!T)val;
> > > }
> > 
> > Yes, this ER asks for such safe function in Phobos.
> 
> But it's better to add a template constraint to that T to be sure it's a
> Typedef.

No need:

/// Instantiating with a non-Typedef will return that type
static assert(is(TypedefType!int == int));

--

[Issue 11675] [ICE] (expression.c line 9217) With text() of a Typedef

[d-bugmail--- via Digitalmars-d-bugs]

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

Bastiaan Veelo  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||basti...@veelo.net
 Resolution|--- |WORKSFORME

--- Comment #1 from Bastiaan Veelo  ---
This seems to work for versions 2.065.0 - 2.066.0. It works for later versions
too, after importing std.conv instead of std.string.

https://run.dlang.io/is/FrkAB9

Tested locally on Windows too, dmd 2.079.0.

--

[Issue 18604] in parameter storage class should be deprecated

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #1 from Seb  ---
https://github.com/dlang/dmd/pull/8021

--

[Issue 18604] New: in parameter storage class should be deprecated

[d-bugmail--- via Digitalmars-d-bugs]

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

  Issue ID: 18604
   Summary: in parameter storage class should be deprecated
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: greensunn...@gmail.com

`in` currently just means `const` even though it was supposed to mean `scope
const`. This makes it redundant and confusing and should be deprecated. Maybe
after it has been deprecated and been an error for one version, it can be
re-introduced with the proper meaning, but for now it should definitely trigger
a deprecation warning.


> Walter: I don't think we can fix in. It may break an astonishing amount of 
> code, since it was never enforced.

See also:

https://github.com/dlang/druntime/pull/2139#issuecomment-372455730
https://dlang.org/spec/function.html#parameters

--

[Issue 13983] RefCounted needs to be pure, @safe, nothrow

[d-bugmail--- via Digitalmars-d-bugs]

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

Carsten Blüggel  changed:

   What|Removed |Added

 CC||chi...@posteo.net

--- Comment #7 from Carsten Blüggel  ---
I' m currently working on a fix for -dip1000 compilable std.algorithm.iteration
which will(?) touch "RefCounted needs to be (some more) @safe" as well, sadly
all by introducing @trusted :-(  ; Am I completely wrong here with @trusted?
These are my current typecons.RefCounted related findings in order to fix
std/algorithm/iteration.d(4245): Error: @safe function
std.algorithm.iteration.__unittest_L4227_C7 cannot call @system function
std.algorithm.comparison.equal!().equal!(Result, string[]).equal   :
```
diff --git a/std/typecons.d b/std/typecons.d
index 3a36bc4..e9f79ba 100644
--- a/std/typecons.d
+++ b/std/typecons.d
@@ -5540,9 +5540,9 @@ if (!is(T == class) && !(is(T == interface)))
 {
 extern(C) private pure nothrow @nogc static // TODO remove pure when
https://issues.dlang.org/show_bug.cgi?id=15862 has been fixed
 {
-pragma(mangle, "free") void pureFree( void *ptr );
+pragma(mangle, "free") void pureFree( void *ptr ) @trusted;
 pragma(mangle, "gc_addRange") void pureGcAddRange( in void* p, size_t
sz, const TypeInfo ti = null );
-pragma(mangle, "gc_removeRange") void pureGcRemoveRange( in void* p );
+pragma(mangle, "gc_removeRange") void pureGcRemoveRange( in void* p )
@trusted;
 }

 /// $(D RefCounted) storage implementation.
@@ -5557,7 +5557,7 @@ if (!is(T == class) && !(is(T == interface)))

 private Impl* _store;

-private void initialize(A...)(auto ref A args)
+private void initialize(A...)(auto ref A args) @trusted
 {
 import core.exception : onOutOfMemoryError;
 import std.conv : emplace;
@@ -5690,7 +5690,7 @@ to deallocate the corresponding resource.
 if (--_refCounted._store._count)
 return;
 // Done, deallocate
-.destroy(_refCounted._store._payload);
+() @trusted { .destroy(_refCounted._store._payload); }();
 static if (hasIndirections!T)
 {
 pureGcRemoveRange(&_refCounted._store._payload);
```

--

[Issue 18597] more unsafe unaligned pointer errors

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #4 from ag0aep6g  ---
(In reply to Walter Bright from comment #2)
> (In reply to ag0aep6g from comment #1)
[...]
> Sorry about that, but I just copy pasted from the public page:
[...]
> I.e. your email address appears with every comment you write, including the
> one this is in reply to. You might want to check your bugzilla profile.

Huh. I thought I had set the name properly. Sorry for lashing out.

Bugzilla didn't already make it public, though. It's smart enough to remove the
domain part in replies and on truly public pages (i.e. when you're not logged
in).

But then again,  shows all Bugzilla
activity to the public, including everyone's addresses. So that's that.

--

[Issue 18580] std.conv.to!(ubyte[])(void[]) should work

[d-bugmail--- via Digitalmars-d-bugs]

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

Steven Schveighoffer  changed:

   What|Removed |Added

 CC||schvei...@yahoo.com

--- Comment #8 from Steven Schveighoffer  ---
There are 2 possibilities I see for this:

1. It doesn't work, use a cast.
2. It should duplicate the array into a new ubyte array.

Simply doing the cast in std.conv.to is not acceptable, even in @system code,
as it's equivalent to a possibly undefined-behavior inducing cast. to is
supposed to be a "safe" cast.

It may be possible to allow a direct cast to const(ubyte)[].

--

[Issue 13727] std.stdio.File not thread-safe

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #15 from Steven Schveighoffer  ---
(In reply to Steven Schveighoffer from comment #14)
> It seems to be passing more frequently, but still seems to have issues:

I take it back, it seems this is the only time the Win32 test has run since you
reopened. So seems not to be fixed.

--

[Issue 13727] std.stdio.File not thread-safe

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #14 from Steven Schveighoffer  ---
It seems to be passing more frequently, but still seems to have issues:
https://auto-tester.puremagic.com/show-run.ghtml?projectid=1=3072904=true

Logged output:
Test runnable/test13727.d failed.  The logged output:
..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   
-odtest_results\runnable -oftest_results\runnable\test13727_0.exe 
runnable\test13727.d  -map nul.map


test_results\runnable\test13727_0.exe




..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -inline
-odtest_results\runnable -oftest_results\runnable\test13727_1.exe 
runnable\test13727.d  -map nul.map


test_results\runnable\test13727_1.exe




..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -release
-odtest_results\runnable -oftest_results\runnable\test13727_2.exe 
runnable\test13727.d  -map nul.map


test_results\runnable\test13727_2.exe




..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -inline
-release -odtest_results\runnable -oftest_results\runnable\test13727_3.exe 
runnable\test13727.d  -map nul.map


test_results\runnable\test13727_3.exe




..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -g
-odtest_results\runnable -oftest_results\runnable\test13727_4.exe 
runnable\test13727.d  -map nul.map


test_results\runnable\test13727_4.exe






std.exception.ErrnoException@std\stdio.d(576): Could not close file
`runnable/extra-files/extra13727.txt' (No error)







0x0040805C in @safe bool std.exception.errnoEnforce!(bool, "std\stdio.d",
576u).errnoEnforce(bool, lazy immutable(char)[])



0x00403BCB in @safe void std.stdio.File.detach()



0x004025CD in void
std.parallelism.ParallelForeach!(immutable(char)[][]).ParallelForeach.opApply(scope
int delegate(ref immutable(char)[])).doIt() at
C:\cygwin\home\braddr\sandbox\at-client\pull-3072904-Win_32\dmd\test\..\..\phobos\std\parallelism.d-mixin-4007(4053)



0x0040CFB1 in void std.parallelism.run!(void delegate()).run(void delegate())



0x00404C24 in void std.parallelism.TaskPool.executeWorkLoop()



0x00431934 in __threadstartex



0x77124A77 in RtlGetAppContainerNamedObjectPath



0x77124A47 in RtlGetAppContainerNamedObjectPath

--

[Issue 9983] inout type can not be used as a parameter for structure template

[d-bugmail--- via Digitalmars-d-bugs]

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

Steven Schveighoffer  changed:

   What|Removed |Added

 CC||schvei...@yahoo.com

--- Comment #2 from Steven Schveighoffer  ---
I actually went over this in my inout talk a few years ago.

a couple of points here:

1. The OP's request is invalid. There is no way for f to know what the
mutability qualifier is, as inout is not a template parameter, it's a
qualifier.

2. inout members should be allowed inside structs, they will work just fine. I
wish they hadn't been disallowed.

The only thing you wouldn't be able to do is call a function that returns a
struct with inout members with a different mutability qualifier than inout.

e.g. this should work:

inout int[] x;
auto foo = f(x); // OK, returns Foo!(inout(int))

But this shouldn't:

int[] x;
auto foo = f(x); // Error, cannot convert struct with inout members to proper
mutability.

There is no way for the compiler to know that it could potentially convert the
return value to mutable T, even when it knows that Foo is a template.

We should either close this bug as invalid, or repurpose to request support for
structs with inout members.

--

[Issue 18585] Linker error if compiled with -dip1000

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=18585
Issue 18585 depends on issue 17961, which changed state.

Issue 17961 Summary: std.uni does not compile with -unittest -dip1000
https://issues.dlang.org/show_bug.cgi?id=17961

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--

[Issue 17961] std.uni does not compile with -unittest -dip1000

[d-bugmail--- via Digitalmars-d-bugs]

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

github-bugzi...@puremagic.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--

[Issue 17961] std.uni does not compile with -unittest -dip1000

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #12 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/cef1c19991f39aa3dda07b08a79d164f6cb352df
Fix Issue 17961 - std.uni does not compile with -unittest -dip1000; rebased

https://github.com/dlang/phobos/commit/92877fddb5fff7b76e95fd35fd50036cb57b9ba4
Merge pull request #6041 from carblue/issue17961

Fix Issue 17961 - std.uni does not compile with -unittest -dip1000

--

[Issue 7804] Cannot alias __traits directly

[d-bugmail--- via Digitalmars-d-bugs]

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

uplink.co...@googlemail.com changed:

   What|Removed |Added

 CC||uplink.co...@googlemail.com

--- Comment #8 from uplink.co...@googlemail.com ---
The issue with this one is that __traits are not considered as types by the
parser as they mostly are not.

one approach could be to have an opinion about which __traits can evaluate to
types and allow those at parser level.

I may give this a shot but my time is currently limited.

--

[Issue 18603] Illegal instruction: 4 on Mac OS 10.7.5 Leopard

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #4 from Seb  ---
(In reply to Silas S. Brown from comment #3)
> There is also a reference to 10.6 in the installer itself.  It says "This
> package is intended for Mac OS X Snow Leopard (10.6) and later" on the
> "Welcome to the DMD2 Installer" screen.

Thanks!
I don't use OS X, but it seems like this should do the deed:

https://github.com/dlang/installer/pull/308

BTW 2.078.3 should still run on 10.7

--

[Issue 18603] Illegal instruction: 4 on Mac OS 10.7.5 Leopard

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #3 from Silas S. Brown  ---
There is also a reference to 10.6 in the installer itself.  It says "This
package is intended for Mac OS X Snow Leopard (10.6) and later" on the "Welcome
to the DMD2 Installer" screen.

--

[Issue 18603] Illegal instruction: 4 on Mac OS 10.7.5 Leopard

[d-bugmail--- via Digitalmars-d-bugs]

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

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com
  Component|installer   |dlang.org

--- Comment #2 from Seb  ---
> I see that this page (https://dlang.org/dmd-osx.html) still says 10.7

PR: https://github.com/dlang/dlang.org/pull/2275

--

[Issue 7804] Cannot alias __traits directly

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #7 from Manu  ---
Plz can has fix?
This is so old!

--

[Issue 18603] Illegal instruction: 4 on Mac OS 10.7.5 Leopard

[d-bugmail--- via Digitalmars-d-bugs]

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

greenify  changed:

   What|Removed |Added

 CC||greeen...@gmail.com

--- Comment #1 from greenify  ---
Yes, the minimal deployment target was bumped to 10.9 with 2.079

See: https://dlang.org/changelog/2.079.0.html#osx-10_9

So I guess the only thing we can do is update the docs.
I see that this page (https://dlang.org/dmd-osx.html) still says 10.7, did you
see another one?

--

[Issue 18597] more unsafe unaligned pointer errors

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #3 from Walter Bright  ---
https://github.com/dlang/dmd/pull/8019

--

[Issue 18601] alias m = __traits(getMember, ...) doesn't work

[d-bugmail--- via Digitalmars-d-bugs]

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

Simen Kjaeraas  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||simen.kja...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #4 from Simen Kjaeraas  ---


*** This issue has been marked as a duplicate of issue 7804 ***

--

[Issue 17571] Cannot create alias of __traits(getMember, ...)

[d-bugmail--- via Digitalmars-d-bugs]

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

Simen Kjaeraas  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||simen.kja...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #4 from Simen Kjaeraas  ---


*** This issue has been marked as a duplicate of issue 7804 ***

--

[Issue 7804] Cannot alias __traits directly

[d-bugmail--- via Digitalmars-d-bugs]

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

Simen Kjaeraas  changed:

   What|Removed |Added

 CC||turkey...@gmail.com

--- Comment #6 from Simen Kjaeraas  ---
*** Issue 18601 has been marked as a duplicate of this issue. ***

--

[Issue 7804] Cannot alias __traits directly

[d-bugmail--- via Digitalmars-d-bugs]

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

Simen Kjaeraas  changed:

   What|Removed |Added

 CC||shac...@weka.io

--- Comment #5 from Simen Kjaeraas  ---
*** Issue 17571 has been marked as a duplicate of this issue. ***

--

[Issue 18282] [Scope][DIP1000]Assignment of local variable to `scope` variable not recognized by compiler

[d-bugmail--- via Digitalmars-d-bugs]

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

Walter Bright  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |---

--- Comment #3 from Walter Bright  ---
I'll reopen it and look at it again.

--

[Issue 13727] std.stdio.File not thread-safe

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #13 from Walter Bright  ---
(In reply to Steven Schveighoffer from comment #12)
> This was pulled in May 2016, so I'm assuming dmd release has been
> updated with new snn.lib?

The test case passes, so yes.

> In any case, there are still threading issues. Not
> sure whether they are all related.

In order to keep this open, it needs specifics.

--

[Issue 18597] more unsafe unaligned pointer errors

[d-bugmail--- via Digitalmars-d-bugs]

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

--- Comment #2 from Walter Bright  ---
(In reply to ag0aep6g from comment #1)
> (In reply to Walter Bright from comment #0)
> > ag0aep6g@[...].com writes:
> 
> Please don't give away people's email addresses like that. It doesn't matter
> too much for me, because that's my D address, but generally it's not a nice
> thing to do.

Sorry about that, but I just copy pasted from the public page:

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

I.e. your email address appears with every comment you write, including the one
this is in reply to. You might want to check your bugzilla profile.

--

[Issue 18592] Associative array assignment with a destructor should be @safe if the destructor is @safe

[d-bugmail--- via Digitalmars-d-bugs]

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

Carsten Blüggel  changed:

   What|Removed |Added

 CC||chi...@posteo.net

--

[Issue 18592] Associative array assignment with a destructor should be @safe if the destructor is @safe

[d-bugmail--- via Digitalmars-d-bugs]

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

Walter Bright  changed:

   What|Removed |Added

 CC||bugzi...@digitalmars.com
   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=18000

--- Comment #1 from Walter Bright  ---
The solution is likely the same as for https://github.com/dlang/dmd/pull/8011

--

[Issue 18000] [scope] auto-generated opAssign not scope aware

[d-bugmail--- via Digitalmars-d-bugs]

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

Walter Bright  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=18592

--

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

[d-bugmail--- via Digitalmars-d-bugs]

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

Carsten Blüggel  changed:

   What|Removed |Added

 CC||chi...@posteo.net

--