On Tuesday, 27 June 2017 at 09:20:40 UTC, Sönke Ludwig wrote:
Am 22.06.2017 um 10:55 schrieb Sönke Ludwig:
There have been some minor fixes and vibe.d 0.8.0-rc.2 and vibe-core 1.0.0-rc.2 have been tagged. The final release is rescheduled for Monday, July the 3rd.

It seems there is an issue with the dmd 2.075.0-b1 and rc.2

vibe-d:utils 0.8.0-rc.2: building configuration "library"...
..\..\..\..\Users\D041451\AppData\Roaming\dub\packages\vibe-d-0.8.0-rc.2\vibe-d\utils\vibe\utils\hashmap.d(258,45):
 Error: function vibe.utils.hashmap.HashMap!(void*, uint, 
DefaultHashMapTraits!(void*)).HashMap.AW (IAllocator a) is not callable using 
argument types (shared(ISharedAllocator))
..\..\..\..\Users\D041451\AppData\Roaming\dub\packages\vibe-d-0.8.0-rc.2\vibe-d\utils\vibe\internal\memory_legacy.d(199,21):
 Error: template instance vibe.utils.hashmap.HashMap!(void*, uint, 
DefaultHashMapTraits!(void*)).HashMap.opIndexAssign!uint error instantiating
..\..\..\..\Users\D041451\AppData\Roaming\dub\packages\vibe-d-0.8.0-rc.2\vibe-d\utils\vibe\internal\memory_legacy.d(199,21):
 Error: function 'vibe.utils.hashmap.HashMap!(void*, uint, 
DefaultHashMapTraits!(void*)).HashMap.opIndexAssign!uint.opIndexAssign' is not 
nothrow
..\..\..\..\Users\D041451\AppData\Roaming\dub\packages\vibe-d-0.8.0-rc.2\vibe-d\utils\vibe\internal\memory_legacy.d(194,9):
 Error: nothrow function 'vibe.internal.memory_legacy.DebugAllocator.alloc' may 
throw
..\..\..\..\Users\D041451\AppData\Roaming\dub\packages\vibe-d-0.8.0-rc.2\vibe-d\utils\vibe\internal\memory_legacy.d(218,21):
 Error: function 'vibe.utils.hashmap.HashMap!(void*, uint, 
DefaultHashMapTraits!(void*)).HashMap.opIndexAssign!uint.opIndexAssign' is not 
nothrow
..\..\..\..\Users\D041451\AppData\Roaming\dub\packages\vibe-d-0.8.0-rc.2\vibe-d\utils\vibe\internal\memory_legacy.d(208,9):
 Error: nothrow function 'vibe.internal.memory_legacy.DebugAllocator.realloc' 
may throw
dmd failed with exit code 1.

Does not occur with 2.074.

Kind regards
André

Reply via email to