Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linear #215

Merged
merged 64 commits into from Oct 10, 2014
Merged

Linear #215

merged 64 commits into from Oct 10, 2014

Conversation

cchalmers
Copy link
Member

Branched version of #212.

Mathnerd314 and others added 30 commits May 27, 2014 18:19
…double

Conflicts:
	src/Diagrams/Tangent.hs
	src/Diagrams/ThreeD/Transform.hs
	src/Diagrams/TwoD/Arrowheads.hs
	src/Diagrams/TwoD/Combinators.hs
	src/Diagrams/TwoD/Image.hs
	src/Diagrams/TwoD/Offset.hs
	src/Diagrams/TwoD/Transform/ScaleInv.hs
* revert using MeasureX
* various R2 -> R2Ish changes
…ish-haskell.yaml -i

Although I had to tweak & untweak some files so stylish-haskell / haskell-src-exts can parse them
…ance, so I might as well have the RealFloat constraint as well.
cchalmers and others added 4 commits September 14, 2014 19:56
It's not actually about points, but it's a utility function for vector
spaces, like the rest of that module, and it doesn't belong under 2D.
@@ -113,6 +109,9 @@ Library
safe >= 0.2 && < 0.4,
JuicyPixels >= 3.1.5 && < 3.2,
hashable >= 1.1 && < 1.3,
linear >= 1.10 && < 2.0,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general Diagrams puts upper bounds at the smallest value that could require code changes, assuming the dependency follows the PVP. That would be something like linear >= 1.10 && < 1.11. Does @ekmettt provide some stronger promise of backwards compatibility for linear < 2.0 that should change that?

@cchalmers
Copy link
Member Author

I just saw linear-accelerate has those bounds. Don't know of any promises add no breaking changes before 2.0.

@bergey
Copy link
Member

bergey commented Sep 19, 2014

This looks really close (including all the other branches). Things I know still need to happen:

  • updating diagrams-doc
  • tightening the bounds to linear < 1.11

Anything else that needs to happen? Can we make a plan to divide up the work of updating -doc? Maybe:

  • manual
  • gallery
  • tutorials

But the manual is probably the most work of those, so we could split it instead.

@jeffreyrosenbluth
Copy link
Member

Sure, I'll start on the gallery.

@cchalmers
Copy link
Member Author

I'll get working on -builder and the tutorials. SVGFonts also needs porting.

@bergey
Copy link
Member

bergey commented Sep 19, 2014

Great. I'll work on the manual.

@byorgey
Copy link
Member

byorgey commented Sep 20, 2014

It sounds like you all have pretty much decided to go ahead with this, which is great. For what it's worth I just thought I would mention that though I haven't had a chance to look through everything, from what I have seen I really like it.

@bergey
Copy link
Member

bergey commented Oct 8, 2014

Is this (finally!) ready to merge?

@cchalmers
Copy link
Member Author

Think so :D

I’d like it if we could hold off releasing about a week. I’m working on some other breaking changes (generalising SizeSpec and a new Measure) in another branch. If they turn out good I’d rather they be included in this realise then have more breaking changes in the next release.

@bergey
Copy link
Member

bergey commented Oct 9, 2014

I was just talking about getting this into master. I have no immediate plan (or time) for a release.

@jeffreyrosenbluth
Copy link
Member

LGTM

@jeffreyrosenbluth
Copy link
Member

@cchalmers I think it's only fitting that you merge this PR

bergey added a commit that referenced this pull request Oct 10, 2014
Migrate from `vector-space` package to `linear`

Make types more polymorphic.
@bergey bergey merged commit 5c64686 into master Oct 10, 2014
@byorgey
Copy link
Member

byorgey commented Oct 10, 2014

OMG!! =D

@bergey bergey deleted the linear branch March 10, 2015 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants