Skip to content

Releases: Seelengrab/FieldFlags.jl

v0.4.0

13 Oct 18:05
9af0ffe
Compare
Choose a tag to compare

There's unfortunately a good, but breaking change necessitating this breaking release. The default-zero arg constructor for any bitfield has been removed. In previous versions, this constructor zero-initialized all fields. This however clashes with a zero-arg constructor for a bitfield that solely consists of padding (which is useful in some contexts), and hence had to be removed. For the same reason, it's not possible to give a deprecation notice. Users are encouraged to transition to the use of zero, which zero-initializes the bitfield just the same as the old zero-arg constructor would have - it is a drop-in replacement :)

New features/other fixes:

  • Fixes some hygiene bugs when calling some of the expression building functions/macros in other external macros.
  • Accessing a field now also returns the smallest possible Unsigned capable of holding the field value, instead of UInt in all cases.
  • A new function bitfieldnames, which gives the names that have been defined for a bitfield. This is the bitfield equivalent to fieldnames, intended to be used in cases where the names of a bitfield purely from a type are required.

Full Changelog: v0.3.9...v0.4.0

v0.3.9

21 Jun 07:18
29f4c59
Compare
Choose a tag to compare

Fixes

Full Changelog: v0.3.8...v0.3.9

v0.3.8

20 Jun 08:09
4f439da
Compare
Choose a tag to compare

General

  • Improve documentation

New Features

  • It is now possible to declare types created via @bitfield and @bitflags as a subtype of an abstract type, with the usual subtyping syntax for structs. #8

Full Changelog: v0.3.7...v0.3.8

v0.3.7

20 Jun 07:31
f06e648
Compare
Choose a tag to compare

Full Changelog: v0.3.6...v0.3.7

v0.3.6

07 Jun 07:55
9d9591e
Compare
Choose a tag to compare
  • #3: Input Constraint Checking

Full Changelog: v0.3.5...v0.3.6

v0.3.5

28 May 12:29
55275a8
Compare
Choose a tag to compare

Initial release with docs 🎉