funny ha ha - Page 22 - Developer IT

What kind of routes could I get back from kAudioSessionProperty_AudioRoute property?

- by mystify

Apple guy tried to be funny and wrote in the docs: ("Headphone," "Speaker," etc.) What kind of return values are possible in reality?

Why does Scala apply thunks automatically, sometimes?

At just after 2:40 in ShadowofCatron's Scala Tutorial 3 video, it's pointed out that the parentheses following the name of a thunk are optional. "Buh?" said my functional programming brain, since the value of a function and the value it evaluates to when applied are completely different things. So I wrote the following to try this out. My thought process is described in the comments. object Main { var counter: Int = 10 def f(): Int = { counter = counter + 1; counter } def runThunk(t: () => Int): Int = { t() } def main(args: Array[String]): Unit = { val a = f() // I expect this to mean "apply f to no args" println(a) // and apparently it does val b = f // I expect this to mean "the value f", a function value println(b) // but it's the value it evaluates to when applied to no args println(b) // and the evaluation happens immediately, not in the call runThunk(b) // This is an error: it's not println doing something funny runThunk(f) // Not an error: seems to be val doing something funny } } To be clear about the problem, this Scheme program (and the console dump which follows) shows what I expected the Scala program to do. (define counter (list 10)) (define f (lambda () (set-car! counter (+ (car counter) 1)) (car counter))) (define runThunk (lambda (t) (t))) (define main (lambda args (let ((a (f)) (b f)) (display a) (newline) (display b) (newline) (display b) (newline) (runThunk b) (runThunk f)))) > (main) 11 #<procedure:f> #<procedure:f> 13 After coming to this site to ask about this, I came across this answer which told me how to fix the above Scala program: val b = f _ // Hey Scala, I mean f, not f() But the underscore 'hint' is only needed sometimes. When I call runThunk(f), no hint is required. But when I 'alias' f to b with a val then apply it, it doesn't work: the evaluation happens in the val; and even lazy val works this way, so it's not the point of evaluation causing this behaviour. That all leaves me with the question: Why does Scala sometimes automatically apply thunks when evaluating them? Is it, as I suspect, type inference? And if so, shouldn't a type system stay out of the language's semantics? Is this a good idea? Do Scala programmers apply thunks rather than refer to their values so much more often that making the parens optional is better overall? Examples written using Scala 2.8.0RC3, DrScheme 4.0.1 in R5RS.

Search Results

Search found 1341 results on 54 pages for 'funny ha ha'.

Page 22/54 | < Previous Page | 18 19 20 21 22 23 24 25 26 27 28 29 | Next Page >

- by mystify

- by Anonymouse

- by di3go

- by user296175

- by mystify

- by reg3n

- by DMan

- by Knowing me knowing you

- by Blankman

- by Rajapandian

- by vasion

- by Can Berk Güder

- by gf

- by DVK

- by Rajapandian

- by user335518

- by Drew Noakes

- by androdevo

- by Starx

- by Pittor

- by Rajapandian

- by Matenia Rossides

- by 01

- by Daniel Severin

- by CrazyJoe

< Previous Page | 18 19 20 21 22 23 24 25 26 27 28 29 | Next Page >