Rob Spoor wrote:Since that compiles, you're not wrong
I knew that lambdas had precedence over casting, but never tried a lambda in a lambda. I am actually surprised that https://docs.oracle.com/javase/tutorial/java/nutsandbolts/operators.html still does not include the lambda operator, even after 18 months of Java 8.
When I try to get an A object using its ID, I get the following error: You have just attempted to access field "bs" yet this field was not detached
Ulf Dittmer wrote:
Hauke Ingmar Schmidt wrote:Are the Java 8 additions for you too minor or not functional?
I didn't say Java had no functional elements, I said that I don't think many (more) will be added.
Ulf Dittmer wrote:but I think it would be a mistake to add everything people want to a language.
Ulf Dittmer wrote:I don't see Oracle putting many functional elements into Java.
Richard Warburton wrote:For many people, what Java 8 offers by way of functional programming is incredibly limited: no monads, no language-level lazy evaluation, no additional support for immutability. As pragmatic programmers, this is fine; what we want is the ability to write library-level abstractions so we can write simple, clean code that solves business problems.
emjee man wrote:NOTE: Since the ad company AND the game's company shut down, THE GAME IS FREE TO USE.
Billy Sclater wrote:Are you saying that Jenkins can be configured to only allow code that builds successfully (and possibly passes sanity and unit tests) to be propogated to master?
Billy Sclater wrote:
Good luck with that!
As a new guy, and a new dev, I have no authority in the company to enforce these changes, I can only suggest them (feeling slightly inappropriate about it, as I'm sure my more experienced collegaues are probably well aware of these solutions!!);( So if my powers of persuasion don't work, I have a choice between being unable to work with a broken environment, or ... attempting a crude 'hack', and having a chance of getting some work done.
Billy Sclater wrote:It sounds like nobody recommends any of the hacks mentioned in this thread! The list above contains 2 of those hacks! But including 'all' in the list above, if you were in my situation, which of the 5 would you choose?
Billy Sclater wrote:Wow! Thats certainly 'saying it how it is'! Actually, I'm a new starter and learning maven. Having broken jars in the repo and broken code on master has pretty much been the norm since I started at the comapny. I thought this was 'normal' and that 'maven was poor build tool'! From what you guys say, quite the reverse! You all seem to be saying:
#1 Building with maven should be a 2 step process S1:Pull the source code S2:mvn clean install.
#2 Using versions as opposed to snapshots is more stable.
#3 There are ways around broken repos but these are 'hacks'. The proper way to do things is not to have a broken repo in the first place (see #2).
Billy Sclater wrote:I thought this was 'normal' and that 'maven was poor build tool'! From what you guys say, quite the reverse!
Billy Sclater wrote:For now looks like I have no choice but to 'hack'!