Bug 17608 – [REG2.075.0-b2] No [] operator overload for type object.TypeInfo_Class

Status
RESOLVED
Resolution
DUPLICATE
Severity
regression
Priority
P1
Component
dmd
Product
D
Version
D2
Platform
All
OS
All
Creation time
2017-07-05T21:02:00Z
Last change time
2017-07-07T00:33:52Z
Assigned to
nobody
Creator
greensunny12

Comments

Comment #0 by greensunny12 — 2017-07-05T21:02:21Z
Both dlang-bot and dlang-tour fail to build with 2.075.0-b2 due a regression manifesting in the build of Vibe.d: https://travis-ci.org/dlang-bots/dlang-bot/jobs/250517978 https://travis-ci.org/dlang-tour/core/jobs/250464149 --------- Log: vibe-d:core 0.7.31: building configuration "libevent"... tiating ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(698): instantiated from here: alloc!(TCPContext*) ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/core/drivers/libevent2_tcp.d(614): instantiated from here: opCall!(TCPContext*) mustache-d 0.1.3: building configuration "library"... vibe-d:utils 0.7.31: building configuration "library"... vibe-d:data 0.7.31: building configuration "library"... ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(ReadWriteMutex) error instantiating ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/core/drivers/libevent2.d(1328): instantiated from here: alloc!() ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(Mutex) error instantiating ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/core/drivers/libevent2.d(1329): instantiated from here: alloc!() ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(Condition, Mutex) error instantiating ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/core/drivers/libevent2.d(1460): instantiated from here: alloc!(Mutex) ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(Libevent2TCPConnection, TCPContext*) error instan../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(OpenSSLStream, Stream, OpenSSLContext, TLSStreamState, string, NetworkAddress) error instantiating ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/utils/memory.d(698): instantiated from here: alloc!(Stream, OpenSSLContext, TLSStreamState, string, NetworkAddress) ../../../.dub/packages/vibe-d-0.7.31/vibe-d/source/vibe/stream/tls.d(152): instantiated from here: opCall!(Stream, OpenSSLContext, TLSStreamState, string, NetworkAddress) dmd failed with exit code 1.
Comment #1 by greensunny12 — 2017-07-06T02:32:38Z
I tried to reproduce this with Digger, upstream/master and upstream/stable, in all three cases Vibe.d passes fine. I only get the errors with dmd-2.075.0-b2 git clone https://github.com/rejectedsoftware/vibe.d git checkout v0.7.31 dub test :core --compiler=/home/seb/dlang/dmd-2.075.0-b2/linux/bin64/dmd Performing "unittest" build using /home/seb/dlang/dmd-2.075.0-b2/linux/bin64/dmd for x86_64. vibe-d:utils 0.7.31: target for configuration "library" is up to date. vibe-d:data 0.7.31: target for configuration "library" is up to date. vibe-d:core 0.7.31: building configuration "vibe-d-core-test-libevent"... source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(ReadWriteMutex) error instantiating source/vibe/core/drivers/libevent2.d(1328): instantiated from here: alloc!() source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(Mutex) error instantiating source/vibe/core/drivers/libevent2.d(1329): instantiated from here: alloc!() source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(Condition, Mutex) error instantiating source/vibe/core/drivers/libevent2.d(1460): instantiated from here: alloc!(Mutex) source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(Libevent2TCPConnection, TCPContext*) error instantiating source/vibe/utils/memory.d(698): instantiated from here: alloc!(TCPContext*) source/vibe/core/drivers/libevent2_tcp.d(614): instantiated from here: opCall!(TCPContext*) source/vibe/utils/memory.d(844): Error: no [] operator overload for type object.TypeInfo_Class source/vibe/utils/memory.d(647): Error: template instance vibe.utils.memory.internalEmplace!(OpenSSLStream, Stream, OpenSSLContext, TLSStreamState, string, NetworkAddress) error instantiating source/vibe/utils/memory.d(698): instantiated from here: alloc!(Stream, OpenSSLContext, TLSStreamState, string, NetworkAddress) source/vibe/stream/tls.d(152): instantiated from here: opCall!(Stream, OpenSSLContext, TLSStreamState, string, NetworkAddress) /home/seb/dlang/dmd-2.075.0-b2/linux/bin64/dmd failed with exit code 1. Is there something different with the build?
Comment #2 by dlang-bugzilla — 2017-07-06T02:40:22Z
(In reply to Seb from comment #1) > Is there something different with the build? Yes. __VERSION__ is 75 instead of 2075.
Comment #3 by greeenify — 2017-07-07T00:33:52Z
Sönke also found this issue, marking this one as a duplicate because his issue has the correct title. *** This issue has been marked as a duplicate of issue 17614 ***