www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - Released vibe.d 0.9.8

reply =?UTF-8?Q?S=C3=B6nke_Ludwig?= <sludwig outerproduct.org> writes:
Just a quick announcement for a new vibe.d release that, probably most 
notably, gets rid of most DIP1000 related deprecation warnings. It also 
brings two breaking changes in the form of deprecating 
vibe.utils.hashmap in favor of the new vibe-container package, as well 
as requiring REST interfaces to be fully  safe.

There is also a bunch of smaller additions and fixes, as listed in the 
change log: https://vibed.org/blog/posts/vibe-release-0.9.8

Although it follows a different version track, vibe-core has also 
received some notable changes during this time frame, such as heavily 
improved performance of ManualEvent, which is the basis for all 
synchronization primitives, a new performInWorker function, 
TaskSemaphore, Monitor!T, yieldUninterruptible and a dedicated thread 
pool for I/O operations.

The next release of vibe.d (0.10.0) is expected to land sooner than 
usual and will contain a substantial restructuring of the package 
structure. All low level modules that are currently sub packages of 
"vibe-d" will be broken out to separate standalone packages, as well as 
the "vibe-d:http" package. This will pave the way for *finally* being 
able to work towards integrating the work on a HTTP/2 implementation 
that was carried out by Francesco Galla during SAoC 2018.
Feb 16
next sibling parent reply aberba <karabutaworld gmail.com> writes:
On Friday, 16 February 2024 at 17:17:35 UTC, Sönke Ludwig wrote:

 Just a quick announcement for a new vibe.d release that, 
 probably most notably, gets rid of most DIP1000 related... as 
 well as requiring REST interfaces to be fully  safe.


How does this affect regular code? What are the implications?
Feb 18
parent =?UTF-8?Q?S=C3=B6nke_Ludwig?= <sludwig outerproduct.org> writes:
Am 19.02.2024 um 00:48 schrieb aberba:

 On Friday, 16 February 2024 at 17:17:35 UTC, Sönke Ludwig wrote:

 Just a quick announcement for a new vibe.d release that, probably most 
 notably, gets rid of most DIP1000 related... as well as requiring REST 
 interfaces to be fully  safe.


 
 How does this affect regular code? What are the implications?


Generally speaking, what has been a `pragma(msg)` based deprecation 
warning during the build for a long time already, now has become a hard 
error (`static assert(false)`). The error should come with the template 
instantiation chain and thus should make it simple to pinpoint the piece 
of code that is ` system`.

The concrete implications are that all interface methods passed to 
`registerRestInterface` must be annotated with ` safe`, as well as all 
functional attributes (` before`/` after`) and all serialized types that 
are part of the interface (e.g. the `toJson`/`fromJson` methods of a 
custom struct that gets returned from an interface function).
Feb 19
prev sibling parent reply =?UTF-8?Q?S=C3=B6nke_Ludwig?= <sludwig outerproduct.org> writes:
 The next release of vibe.d (0.10.0) is expected to land sooner than 
 usual and will contain a substantial restructuring of the package 
 structure. All low level modules that are currently sub packages of 
 "vibe-d" will be broken out to separate standalone packages, as well as 
 the "vibe-d:http" package. This will pave the way for *finally* being 
 able to work towards integrating the work on a HTTP/2 implementation 
 that was carried out by Francesco Galla during SAoC 2018.


0.10.0 is now out and is identical to 0.9.8, apart from the new package 
structure: https://vibed.org/blog/posts/vibe-release-0.10.0

Compatibility with the old structure is still there, but will get 
deprecated in one of the next releases, so a dependency like 
"vibe-d:http" 0.9.x should eventually be adjusted to "vibe-http" 1.x.x.
Feb 19
parent reply aberba <karabutaworld gmail.com> writes:
On Monday, 19 February 2024 at 08:45:28 UTC, Sönke Ludwig wrote:

 The next release of vibe.d (0.10.0) is expected to land sooner 
 than usual and will contain a substantial restructuring of the 
 package structure. All low level modules that are currently 
 sub packages of "vibe-d" will be broken out to separate 
 standalone packages, as well as the "vibe-d:http" package. 
 This will pave the way for *finally* being able to work 
 towards integrating the work on a HTTP/2 implementation that 
 was carried out by Francesco Galla during SAoC 2018.


 0.10.0 is now out and is identical to 0.9.8, apart from the new 
 package structure: 
 https://vibed.org/blog/posts/vibe-release-0.10.0

 Compatibility with the old structure is still there, but will 
 get deprecated in one of the next releases, so a dependency 
 like "vibe-d:http" 0.9.x should eventually be adjusted to 
 "vibe-http" 1.x.x.


On the tutorials section of the vibed.org site, the are links to 
tutorials on my website (aberba.com) however I recently rebuilt 
my website and the links will need adjustment. I can't however 
find where the make a PR for that.
Feb 19
parent =?UTF-8?Q?S=C3=B6nke_Ludwig?= <sludwig outerproduct.org> writes:
Am 19.02.2024 um 19:28 schrieb aberba:

 On the tutorials section of the vibed.org site, the are links to 
 tutorials on my website (aberba.com) however I recently rebuilt my 
 website and the links will need adjustment. I can't however find where 
 the make a PR for that.


The tutorials are listed here: 
https://github.com/vibe-d/vibed.org/blob/master/views/tutorials.dt
Feb 24