Did you try to run "dub upgrade"
Thanks! It's work!
On Tuesday, 11 August 2015 at 16:11:29 UTC, Sönke Ludwig wrote:
Did you try to run "dub upgrade" again after the clean-caches?
This is necessary, because dub.selections.json is supposed to
be able to manually override dependency specifications in
dub.json.
I have a script called dubrenew.sh
On Wednesday, 12 August 2015 at 09:42:20 UTC, ponce wrote:
I have a script called dubrenew.sh
--8<-
#!/bin/bash
rm dub.selections.json
dub clean-caches
--8<-
Works every time (dub upgrade can be used alternatively to
deleting dub.selections.json)
May
On Tue, Aug 11, 2015 at 3:48 PM, Adam D. Ruppe via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> ...
> Most "dynamic" types really are static, you just don't always know the
> layout at compile time. But with a bit of ahead-of-time analyzers of the
> data, we can basicall
Am 11.08.2015 um 16:14 schrieb Suliman:
I still can't get 0.7.24. My config is:
"dependencies": {
"vibe-d": "0.7.24"
},
D:\code\httpApp>dub clean-caches
D:\code\httpApp>dub build
(...)
C:\Users\bubenkov_di\AppData\Roaming\dub\packages\...
Selected package vibe-d 0.7.23 does not match the depen
On Tuesday, 11 August 2015 at 14:14:10 UTC, Suliman wrote:
I still can't get 0.7.24. My config is:
"dependencies": {
"vibe-d": "0.7.24"
},
[...]
Try going to your packages directory and actually deleting the
0.7.23 folder?
(Remember, backup!)
I still can't get 0.7.24. My config is:
"dependencies": {
"vibe-d": "0.7.24"
},
D:\code\httpApp>dub clean-caches
D:\code\httpApp>dub build
Fetching vibe-d 0.7.23 (getting selected version)...
Placing vibe-d 0.7.23 to
C:\Users\bubenkov_di\AppData\Roaming\dub\packages\...
Selected package vibe-d
Am 11.08.2015 um 15:28 schrieb Suliman:
I can't understand why I can't build vibed with 2.068
C:\Users\bubenkov_di\AppData\Roaming\dub\packages\vibe-d-0.7.23\source\vibe\core\drivers\libevent2.d(631):
Error: '_d_monitorenter' is not nothrow
C:\Users\bubenkov_di\AppData\Roaming\dub\packages\vibe-
On Monday, 10 August 2015 at 18:23:25 UTC, Sönke Ludwig wrote:
The main technical reason was CT reflections issues (the
particular case was that they had always been erroneously
recognized as input ranges) and the fact that any API change
involving the Json struct would potentially be a silentl
I can't understand why I can't build vibed with 2.068
C:\Users\bubenkov_di\AppData\Roaming\dub\packages\vibe-d-0.7.23\source\vibe\core\drivers\libevent2.d(631):
Error: '_d_monitorenter' is not nothrow
C:\Users\bubenkov_di\AppData\Roaming\dub\packages\vibe-d-0.7.23\source\vibe\core\drivers\libeve
On Monday, 10 August 2015 at 17:27:56 UTC, Sönke Ludwig wrote:
A new vibe.d release is out. Apart from support for the 2.068 D
frontend, some of the major changes are:
- The vibe.web.web module adds support for convenient
WebSocket routes
- Renamed "SSL" to "TLS" (with compatibility aliases,
Am 10.08.2015 um 19:32 schrieb Adam D. Ruppe:
On Monday, 10 August 2015 at 17:27:56 UTC, Sönke Ludwig wrote:
- Json.opDispatch and Bson.opDispatch are scheduled for deprecation
What was your reason for doing that? I find they are kinda convenient
but also have a way of messing with compile ti
On Monday, 10 August 2015 at 17:27:56 UTC, Sönke Ludwig wrote:
- Json.opDispatch and Bson.opDispatch are scheduled for
deprecation
What was your reason for doing that? I find they are kinda
convenient but also have a way of messing with compile time duck
typing so I restrict it but overa
A new vibe.d release is out. Apart from support for the 2.068 D
frontend, some of the major changes are:
- The vibe.web.web module adds support for convenient WebSocket routes
- Renamed "SSL" to "TLS" (with compatibility aliases, of course)
- Json.opDispatch and Bson.opDispatch are scheduled
14 matches
Mail list logo
