Search results
Jump to navigation
Jump to search
Page title matches
- then there would be certainly less confusion.1 KB (161 words) - 07:16, 11 April 2008
- 1 KB (146 words) - 00:16, 8 September 2020
Page text matches
- ...uld require a Legacy module for backwards compatability, and it may reduce confusion over what the function actually does, because Haskell's <hask>return</hask>680 bytes (108 words) - 20:46, 1 January 2011
- then there would be certainly less confusion.1 KB (161 words) - 07:16, 11 April 2008
- <code>amid</code>, in [[Strictness without ordering, or confusion]].1 KB (175 words) - 22:53, 15 April 2020
- but there is still room for confusion because the first lines mentiones the type `[Char]` which does not appear i2 KB (317 words) - 10:49, 8 November 2016
- ...renamed type parameter "<hask>src</hask>" to "<hask>cur</hask>", to avoid confusion with <hask>Source</hask> in Phooey's use of DataDriven.3 KB (440 words) - 17:28, 18 March 2008
- ...presumes counting element positions starts at 1, perhaps causing needless confusion.2 KB (354 words) - 14:31, 5 January 2024
- ...e is some subtlety that I'm not able to see right now." There is no longer confusion with the interference of6 KB (937 words) - 05:34, 10 December 2020
- ...isn’t with the technical invention–which I like. Rather, I’m cranky about confusion and misleading communication, and about distraction from what we originally4 KB (506 words) - 06:17, 20 April 2024
- ...ly be missed if the programmer isn't conscientious enough, and could cause confusion if they're left in. ...ant, I like {-# LANGUAGE AutoHidingImports #-}, but maybe that would cause confusion if nothing is actually being hidden. PermissiveImports is more general, but9 KB (1,515 words) - 23:39, 23 October 2014
- ...e first version should likely be noted to be an odds-only SoE to avoid any confusion and the second labeled as TH eliminated.7 KB (1,171 words) - 11:56, 21 February 2023
- Thanks for reading the paper! Let me see if I understand your confusion. This thing:8 KB (1,253 words) - 21:53, 12 June 2009
- ForeignPtr -- rename to FinalisedPtr? to void confusion with Foreign.Ptr7 KB (717 words) - 05:40, 25 April 2012
- ...to [https://github.com/haskell/network/issues/7 spurious bug reports] and confusion. It also doesn't seem possible to account for these API differences without8 KB (1,252 words) - 13:33, 4 August 2011
- There has been confusion about the distinction between [[error]]s and [[exception]]s for a long time This is like the confusion between [[Parallelism vs. Concurrency|parallelism and concurrency]].16 KB (2,728 words) - 16:45, 23 July 2019
- of the same amount of confusion for just about anyone else who has approached7 KB (1,266 words) - 05:13, 15 October 2016
- ...en adding a component to your module name, ask yourself if it resolves any confusion or prevents any ambiguity. I would argue that in <tt>Codec.Binary.UTF8.Gene6 KB (939 words) - 15:22, 19 October 2014
- ...windows aren't handled by a layout so they don't get any decoration). This confusion should be prevented. It might be enough to just add another button to the d9 KB (1,449 words) - 23:16, 26 November 2011
- It's not clear why I made this mistake -- I think the seeds of my confusion may have been laid by the form of I don't know if this was just a personal confusion, or more widely experienced.31 KB (5,175 words) - 04:59, 9 March 2011
- confusion).9 KB (1,379 words) - 04:11, 14 February 2023
- The reason coding can be expressed this way in Haskell without undue confusion is because of its extreme conciseness. The habits you've had to learn to m15 KB (2,547 words) - 21:58, 29 October 2011