New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dmd 2.081.0 build fails #2215

Closed
Extrawurst opened this Issue Oct 1, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@Extrawurst
Contributor

Extrawurst commented Oct 1, 2018

looks like currently vibe does not keep up being compatible with current dmd versions anymore. dmd 2.080.1 is the last supported one, already with 2.081 it fails to build - current dmd version is 2.082 already.

vibe-d:stream 0.8.4: building configuration "library"...
../../../.dub/packages/vibe-d-0.8.4/vibe-d/stream/vibe/stream/wrapper.d(179,22): Error: no property connected for type const(InterfaceProxy!(ConnectionStream))
../../../.dub/packages/vibe-d-0.8.4/vibe-d/stream/vibe/stream/wrapper.d(187,19): Error: no property connected for type InterfaceProxy!(ConnectionStream)
../../../.dub/packages/vibe-d-0.8.4/vibe-d/stream/vibe/stream/wrapper.d(188,15): Error: no property close for type InterfaceProxy!(ConnectionStream)
../../../.dub/packages/vibe-d-0.8.4/vibe-d/stream/vibe/stream/wrapper.d(198,22): Error: no property waitForData for type InterfaceProxy!(ConnectionStream)
@Extrawurst

This comment has been minimized.

Show comment
Hide comment
@Extrawurst

Extrawurst Oct 2, 2018

Contributor

Just realised how long there was no activity on the project here. Is vibe.d discontinued? see also http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/65001/

Contributor

Extrawurst commented Oct 2, 2018

Just realised how long there was no activity on the project here. Is vibe.d discontinued? see also http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/65001/

@s-ludwig

This comment has been minimized.

Show comment
Hide comment
@s-ludwig

s-ludwig Oct 2, 2018

Member

I'm currently preparing eventcore and vibe-core to be tested on the latest versions. But I was unter the impression that the project tester is still testing vibe.d to make sure that there are no DMD/Phobos/Druntime regressions. Anyway, I'll look into this afterwards.

But no, the development is not discontinued, but I'm currently not really able to contribute. This is also true for DUB and the other projects. Basically the only exceptions are occasional fixes in eventcore/vibe-core that are needed for our internal project and occasional PR reviews. This will change once the project is on the market.

There is also the ongoing HTTP/2 SAoC project, which happens in the separate vibe-http repository, so if everything goes right, there should finally be basic HTTP/2 functionality by the end of the year.

Member

s-ludwig commented Oct 2, 2018

I'm currently preparing eventcore and vibe-core to be tested on the latest versions. But I was unter the impression that the project tester is still testing vibe.d to make sure that there are no DMD/Phobos/Druntime regressions. Anyway, I'll look into this afterwards.

But no, the development is not discontinued, but I'm currently not really able to contribute. This is also true for DUB and the other projects. Basically the only exceptions are occasional fixes in eventcore/vibe-core that are needed for our internal project and occasional PR reviews. This will change once the project is on the market.

There is also the ongoing HTTP/2 SAoC project, which happens in the separate vibe-http repository, so if everything goes right, there should finally be basic HTTP/2 functionality by the end of the year.

@wilzbach

This comment has been minimized.

Show comment
Hide comment
@wilzbach

wilzbach Oct 2, 2018

Contributor

This is a known regression which was the reason for the quick 2.081.1 follow-up.
See #2181

Contributor

wilzbach commented Oct 2, 2018

This is a known regression which was the reason for the quick 2.081.1 follow-up.
See #2181

@wilzbach wilzbach closed this Oct 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment