class scala[A] { def apply[B](f: (A) => B) = directly to forehead }

Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > class scala[A] { def apply[B](f: (A) => B) = directly to forehead }

kugutsu: Dec 31, 2008

Never use postfix ops (which is what calling getFile there without the dot is). They're ambiguous and don't really improve readability in any circumstance. If you want to use a trailing method call with infix invocation, you can group the infix part with parentheses.

code:

(listA ++ listB).tail

For infix notation in general, I would recommend against it except for operators or when using higher order functions. It's fashionable (and recommended by the style guide) to chain higher order functions like so:

code:

things filter (_.someCondition) map (_.toOtherThing)

The reasons they give for this are dubious, but it's pretty popular. From what I've seen, overuse of infix method invocation makes scala code difficult to read, so I tend to be pretty conservative about using it.

# ¿ Jul 20, 2016 05:03

Adbot: ADBOT LOVES YOU

# ¿ May 12, 2024 05:52

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > class scala[A] { def apply[B](f: (A) => B) = directly to forehead }