Skip to content

Releases: ericphanson/AllocArrays.jl

v1.1.0

26 Mar 11:31
fde16d1
Compare
Choose a tag to compare

AllocArrays v1.1.0

Diff since v1.0.0

Merged pull requests:

v1.0.0

25 Mar 10:56
0ff7cca
Compare
Choose a tag to compare

AllocArrays v1.0.0

Diff since v0.4.2

Breaking changes

  • set default buffer to a new AutoscalingAllocBuffer which can grow and reuse memory between batches
  • mark the default buffer as able to change in non-breaking releases of AllocArrays

Merged pull requests:

  • add AutoscalingAllocBuffer and make default. Mark as v1.0 (#25) (@ericphanson)

v0.4.2

21 Mar 18:01
c7aac53
Compare
Choose a tag to compare

AllocArrays v0.4.2

Diff since v0.4.1

Merged pull requests:

v0.4.1

20 Mar 04:04
9e63095
Compare
Choose a tag to compare

AllocArrays v0.4.1

Diff since v0.4.0

Merged pull requests:

v0.4.0

20 Mar 00:21
f00de68
Compare
Choose a tag to compare

AllocArrays 0.4.0

Breaking

  • reverts to the v0.2 way of doing things (see #20)
  • in comparison to v0.2 adds no-op constructors so AllocArray(a::AllocArray) just returns a
    Diff since v0.3.0

Merged pull requests:

  • rm UnsafeArrays, use previous way (#20)
  • Breaking: always represent inner array as UnsafeArray (#18)

Closed issues:
None

v0.3.0

20 Mar 00:21
0f7dfc9
Compare
Choose a tag to compare

AllocArrays 0.3.0

Breaking

  • AllocArray now only has 2 type parameters T and N and subtypes DenseArray{T,N}
  • an array arr must be representable by UnsafeArrays for AllocArray(arr) to succeed. That means ranges like 1:4 must be collected before being passed to AllocArray
    Diff since v0.2.0

Merged pull requests:

  • Breaking: always represent inner array as UnsafeArray (#18)
  • Update Bumper compat to v0.7 (#17)

Closed issues:
None

v0.1.1

12 Nov 00:02
9939bb8
Compare
Choose a tag to compare

AllocArrays v0.1.1

Diff since v0.1.0

  • minimal update to support Bumper.jl v0.5

Merged pull requests:

v0.1.0

28 Oct 23:47
ac1d45e
Compare
Choose a tag to compare

AllocArrays v0.1.0

Merged pull requests:

Closed issues:

  • Possible memory safety features (#9)