RejectedSoftware Forums

On Mon, 10 Jul 2017 12:12:29 GMT, Sönke Ludwig wrote:

After a long journey - it took over eight months - the new core package is finally ready. Along with it, version 0.8.0 of vibe.d is released. This marks a major milestone in vibe.d's development.

Apart from offering support for using the new core package, 0.8.0 now also employs @safe and nothrow where possible, making it possible to write fully @safe vibe.d applications. And of course, as always, there is also a long list of other improvements and bug fixes.

The core package can be considered as a complete rewrite of the original vibe-d:core package, retaining a mostly backwards compatible API from a library user's point of view. Lots of changes went into modernizing the code and removing inherent performance limits of the previous design*.

See the dedicated blog post for a basic explanation of the changes:
https://vibed.org/blog/posts/introducing-vibe-core

The change log for vibe.d 0.8.0 is listed here:
https://vibed.org/blog/posts/vibe-release-0.8.0

Finally, to make use of the vibe-core module, which is highly recommended outside of critical production systems, you'll have to manually enable it in the package recipe of your project:

• dub.sdl:

  dependency "vibe-d:core" version="~>0.8.0"
  subConfiguration "vibe-d:core" "vibe-core"
  

• dub.json:

  {
      ...
      "dependencies" : {
          ...
          "vibe-d:core": "~>0.8.0"
      },
      "subConfigurations": {
          ...
          "vibe-d:core": "vibe-core"
      }
  }
  

DUB packages:
https://code.dlang.org/packages/vibe-d/0.8.0
https://code.dlang.org/packages/vibe-core/1.0.0

* Note that no dedicated performance tuning has been done yet, so performance levels are expected to still be on a similar level.

When I try to build at Windows 10, dmd 2.074.1 I get the following errors:

Performing "debug" build using dmd for x86.
taggedalgebraic 0.10.7: target for configuration "library" is up to date.
eventcore 0.8.12: target for configuration "winapi-optlink" is up to date.
vibe-core 1.0.0: building configuration "winapi-optlink"...
..\..\AppData\Roaming\dub\packages\vibe-core-1.0.0\vibe-core\source\vibe\core\core.d(1297,3): Error: undefined identifier 'driverCore'
dmd failed with exit code 1.

On Mon, 10 Jul 2017 19:42:59 +0200, Sönke Ludwig wrote:

Am 10.07.2017 um 17:53 schrieb Daniel Vieira:

When I try to build at Windows 10, dmd 2.074.1 I get the following errors:

Performing "debug" build using dmd for x86.
taggedalgebraic 0.10.7: target for configuration "library" is up to date.
eventcore 0.8.12: target for configuration "winapi-optlink" is up to date.
vibe-core 1.0.0: building configuration "winapi-optlink"...
..\..\AppData\Roaming\dub\packages\vibe-core-1.0.0\vibe-core\source\vibe\core\core.d(1297,3): Error: undefined identifier 'driverCore'
dmd failed with exit code 1.

Looks like I forgot some old code there. Workaround is to remove
VibeIdleCollect from the package recipe. I'll adapt this for the new code.

Fixed: 87296bb

On 10.07.17 14:12, Sönke Ludwig wrote:

After a long journey - it took over eight months - the new core package is finally ready. Along with it, version 0.8.0 of vibe.d is released. This marks a major milestone in vibe.d's development.

Thats fantastic news. I only have a very small vibe.d app at home
running on my raspberries, but updating worked very smooth! I only had
to fix some of the @safe warnings, and after 10min, everything worked
again, better than ever! Thanks for this update!

christian

On Mon, 10 Jul 2017 12:12:29 GMT, Sönke Ludwig wrote:

After a long journey - it took over eight months - the new core package is finally ready. Along with it, version 0.8.0 of vibe.d is released. This marks a major milestone in vibe.d's development.

I couldn't find the github repo for the blog post (I had a vague idea the blog was on github), so here go two suggestions:

• "The package in it's original form" -> "its"

• "A lot of things about the D language have been different at that time." -> "were different at that time"