Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: palatable/lambda
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: lambda-1.3
Choose a base ref
...
head repository: palatable/lambda
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: lambda-1.4
Choose a head ref
  • 8 commits
  • 50 files changed
  • 1 contributor

Commits on Jul 31, 2016

  1. Configuration menu
    Copy the full SHA
    02683b6 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    4222b41 View commit details
    Browse the repository at this point in the history
  3. Adding javadoc link to README

    jnape authored Jul 31, 2016
    Configuration menu
    Copy the full SHA
    1e0be65 View commit details
    Browse the repository at this point in the history

Commits on Aug 1, 2016

  1. Adding TOC to Readme

    jnape authored Aug 1, 2016
    Configuration menu
    Copy the full SHA
    ace8e90 View commit details
    Browse the repository at this point in the history

Commits on Aug 2, 2016

  1. Adding Notes to README

    jnape authored Aug 2, 2016
    Configuration menu
    Copy the full SHA
    e6b35f6 View commit details
    Browse the repository at this point in the history

Commits on Aug 7, 2016

  1. For better Java8 compatibility, all lambda input argument types are r…

    …eplaced with Java8 input types where possible
    
     - Fn1 argument types become j.u.f.Function
     - Fn2 argument types become j.u.f.BiFunction
     - Adding Fn2#toBiFunction
    
     - Well, Java8's type hierarchy and javac really worked together on this one. Not only is it not possible for both Fn1 and Fn2 to extend their
        native Java8 counterparts (j.u.f.Function and j.u.f.BiFunction, respectively), due to Function and BiFunction existing in orthogonal type
        hierarchies and both defining conflicting methods with the other; it is also not possible to provide overloads for both Fn1 and Function
        (or Fn2 and BiFunction), since both will be @FunctionInterfaces, and javac will have no opinion about precedence of one over the other.
        The outcome is that explicit, dreadful type-casts to something like (Fn1<Something, OtherThing>) or
        (BiFunction<First, Second, Output>) would be necessary at the call site of every overload. This is the least acceptable outcome for me,
        so I'm begrudgingly just typing against native Java8 types for all inputs. I'm sorry. This is why we can't have nice things.
    jnape committed Aug 7, 2016
    Configuration menu
    Copy the full SHA
    b754519 View commit details
    Browse the repository at this point in the history
  2. Fixing indentation in TOC

    jnape authored Aug 7, 2016
    Configuration menu
    Copy the full SHA
    85d81d5 View commit details
    Browse the repository at this point in the history

Commits on Aug 8, 2016

  1. Configuration menu
    Copy the full SHA
    1714f32 View commit details
    Browse the repository at this point in the history
Loading