Changes in 0.5

[daanhb]

With #78 there were some name changes:

• IntersectionDomain -> IntersectDomain
• DifferenceDomain -> SetdiffDomain

There are three trio's of functions:

• union, uniondomain and UnionDomain
• setdiff, setdiffdomain and SetdiffDomain
• intersect, intersectdomain and IntersectDomain

The idea is similar in all three cases. The union function is the generic Julia function that is invoked with the cup symbol. If one of the arguments is a Domain, then uniondomain is invoked. The latter can also be invoked directly: the difference is that uniondomain treats all its arguments as if they are domains, even if they are not <:Domain. So this allows you to create the union of an interval and a vector, for example. Finally, UnionDomain always returns a UnionDomain type, whereas uniondomain may do some simplifications and return something else (that is functionally equivalent to the actual union).

For intervals, uniondomain differes from union, with the latter following IntervalSets (which throws error if two intervals do not overlap) and uniondomain always returning something that represents the union. This makes uniondomain, intersectdomain and setdiffdomain potentially type-unstable (this is unavoidable and was already the case with set operations). For type-stability, use UnionDomain.

• interval_map(a,b,c,d) is no longer exported. A new mapto function is in the works which is more general: mapto(a..b, c..d) returns a map from a..b to c..d. The idea is that this will work for many other domains as well. It works by associating domains with a canonicaldomain, which allows automatic discovery of maps between many more domains than you explicitly program (for example from any interval a..b to a circle). Needs some more work, though.

• There is now a special type for rectangles and cubes. The ProductDomain and ProductDomain{T} constructors now recognize when a list of intervals is given and they return a more specialized type. Boxes are simple and relevant enough to support better, I thought. I find working with abstract constructors very convenient for that purpose. Most functionality is implemented at the abstract level, so extending is very easy, and it is always the case that the result is <:ProductDomain.

• There is a UnitCube (a product of UnitInterval), but also [-1,1]^d has its own stateless type now, as do all the other fixed intervals: const ChebyshevProductDomain{N,T} = FixedIntervalProduct{ChebyshevInterval{T},N,T}

• I revised the hierarchy of unit balls, unit spheres and unit simplices. Again, an abstract constructor: UnitBall(Val(3)) and UnitBall(3) replace the previous EuclideanUnitBall (now just an alias) and VectorUnitBall (again just an alias).

• The in and approx_in functions are now implemented using promotion. It is functionally the same as before, but cleaner, and it allows concrete domains to intervene when necessary (for example by being more flexible in membership, or more strict).

[daanhb]

I probably left out a few things. I could not get deprecations to work correctly and I simply left them out... We are going from 0.4 to 0.5 series so that is probably fine.

[daanhb]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/35742

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.0 -m "<description of version>" 624873556a52480983ff7db425730ff17e7a93d1
git push origin v0.5.0

[daanhb]

I had packages downstream relying on the changes so I released v0.5... Hopefully it will be straightforward to update ApproxFun @dlfivefifty. It should be fine, except for having to import components and ncomponents from DomainSets (or from CompositeTypes) now.

[daanhb]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/36088

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.1 -m "<description of version>" fe5cb0a8ca754859702d78962216144c440a4d62
git push origin v0.5.1

[daanhb]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/36460

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.2 -m "<description of version>" 481141b88d4e8c632da7ae65b9dd8a6208d122e4
git push origin v0.5.2

[daanhb]

Update: I've changed the canonical domain of an interval to be [-1,1] rather than [0,1]. This will be in 0.5.3.

[daanhb]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/43535

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.3 -m "<description of version>" 5b3904a11f93cba45866085ba7aaa03b11850924
git push origin v0.5.3

[daanhb]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/43643

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.4 -m "<description of version>" 8e9fc19351017781db80483df1665de0b8108dee
git push origin v0.5.4

[daanhb]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/44774

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.5 -m "<description of version>" 64984430e78c97f14294fb1378451ec3e8ffea53
git push origin v0.5.5