Changelog

What's new in GFM version 5:

Breaking changes:

• gfm:net and gfm:enet subpackages have been removed. It turns out nobody was using them. If you need them, stay at ~>4.0.

What's new in GFM version 4:

Breaking changes:

• dropped support for compilers with < 2.067 frontend. GDC is unsupported until it reaches 2.067.
• gfm:math has been split in two packages. All things rather useless were put into a gfm:integers package which contains:
  • half floating-point numbers in gfm.integers.half
  • wide integers in gfm.integers.wideint
  • fixed-point numbers in gfm.integers.fixedpoint
  • rational numbers in gfm.integers.rational
• gfm:image now depends on imageformats version 5. This shouldn't affect your code at all.
• all deprecated aliases and functions gone. The close() function are gone for real.
• no more dependency on the logger package. From now on only std.experimental.logger is used.
• no more predefined aliases for matrices of unsigned integers.

What's new in GFM version 3:

Breaking changes:

• gfm:image now uses the imageformats package as a dependency (https://github.com/lgvz/imageformats). The function for image loading is still loadImage and should work identically. This unbreaks JPEG loading. gfm.image.stb_imageis gone. No more GIF loading but I don't know if it even worked and you get TGA loading instead.
• gfm.math.funcs.min and gfm.math.funcs.max were removed since they already exist in std.algorithm.
• The close()functions are all gone! The new behaviour of destructors is to assert if an actual resource release happen while called by the GC (this assert does not trigger in release mode). So relying on the GC for accidental resource release is now a bug. You can use .destroy instead to call the destructor for a class object in replacement for calling close().
• gfm:mathis not compatible anymore with front-ends prior 2.066

Features:

• Derelict loaders aren't unloaded anymore when the library object disappear. Should allow eg. other OpenGL libraries to work with GFM.