Newest at the top
| 2024-11-01 12:20:29 +0100 | <Rembane> | Hecate: Still at Chalmers! I'll be done any day now. :D |
| 2024-11-01 12:20:21 +0100 | <lambdabot> | (Ord c, ?n::c, Num c) => c |
| 2024-11-01 12:20:20 +0100 | <mauke> | :t head . dropWhile (< ?n) . iterate (2 *) $ 1 |
| 2024-11-01 12:20:15 +0100 | <sprotte24> | ok. if I use binary number, the Powers of 2 have the format 1, 10 100 1000 and so on |
| 2024-11-01 12:19:23 +0100 | <Hecate> | Rembane: I'm not doing too bad! Still at Chalmers? |
| 2024-11-01 12:18:46 +0100 | <Hecate> | damnit I was about to suggest that hahahaha |
| 2024-11-01 12:18:38 +0100 | <mauke> | like bit shifts? |
| 2024-11-01 12:18:33 +0100 | <mauke> | define "using binary" |
| 2024-11-01 12:18:23 +0100 | <sprotte24> | The restriction: using binary is forbidden. |
| 2024-11-01 12:18:22 +0100 | <Rembane> | Hecate: Suuuuuuuuuuuuuuuuuup! :D |
| 2024-11-01 12:18:15 +0100 | <mauke> | yeah, that actually makes things easier |
| 2024-11-01 12:18:03 +0100 | <Hecate> | mauke: maybe they have to round to the highest power of 2 |
| 2024-11-01 12:17:41 +0100 | <sprotte24> | Yes. kome work |
| 2024-11-01 12:17:35 +0100 | <mauke> | I'd say it's 8 |
| 2024-11-01 12:17:21 +0100 | <sprotte24> | n= 9 nearest Power is 16 |
| 2024-11-01 12:16:42 +0100 | <mauke> | oh, is this homework? |
| 2024-11-01 12:16:37 +0100 | <sprotte24> | Example: |
| 2024-11-01 12:16:34 +0100 | <Hecate> | sprotte24: nice |
| 2024-11-01 12:16:28 +0100 | <sprotte24> | The Haskell programm has to compute the nearest Power of two for a given n. |
| 2024-11-01 12:16:25 +0100 | <Hecate> | what's uuuuup |
| 2024-11-01 12:16:19 +0100 | <Hecate> | rembaaaaaaane |
| 2024-11-01 12:15:51 +0100 | <mauke> | what's it do? |
| 2024-11-01 12:15:47 +0100 | <sprotte24> | Hi, Rembane |
| 2024-11-01 12:15:35 +0100 | <sprotte24> | I want to write a Haskell program |
| 2024-11-01 12:15:21 +0100 | <Rembane> | Hi sprotte24 ! |
| 2024-11-01 12:15:11 +0100 | <sprotte24> | Hi |
| 2024-11-01 12:12:28 +0100 | sprotte24 | (~sprotte24@p200300d16f13bb00e9ebafc1049584f7.dip0.t-ipconnect.de) |
| 2024-11-01 12:01:23 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
| 2024-11-01 11:56:29 +0100 | k_hachig_ | (~k_hachig@2607:fea8:351d:ef0:901a:fefb:e87f:78b3) (Ping timeout: 260 seconds) |
| 2024-11-01 11:50:41 +0100 | k_hachig_ | (~k_hachig@2607:fea8:351d:ef0:901a:fefb:e87f:78b3) k_hachig |
| 2024-11-01 11:32:58 +0100 | misterfish | (~misterfis@84.53.85.146) (Ping timeout: 252 seconds) |
| 2024-11-01 11:32:18 +0100 | chele | (~chele@user/chele) chele |
| 2024-11-01 11:27:26 +0100 | <absence> | I see, thanks! |
| 2024-11-01 11:27:12 +0100 | <tomsmeding> | using a let-binding is the only way to set implicit parameters |
| 2024-11-01 11:26:55 +0100 | <absence> | mauke: Less clutter, and clearer intent. |
| 2024-11-01 11:26:19 +0100 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 260 seconds) |
| 2024-11-01 11:25:46 +0100 | <tomsmeding> | `let ?param = _ in f x y z` |
| 2024-11-01 11:25:38 +0100 | <tomsmeding> | you can create the binding locally |
| 2024-11-01 11:25:37 +0100 | <mauke> | why without creating a binding? |
| 2024-11-01 11:25:15 +0100 | <absence> | Is it possible to pass an implicit parameter explicitly, without creating a binding in the calling scope? |
| 2024-11-01 11:22:45 +0100 | absence | (torgeihe@hildring.pvv.ntnu.no) absence |
| 2024-11-01 11:22:06 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2024-11-01 11:21:49 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
| 2024-11-01 11:19:45 +0100 | zmt00 | (~zmt00@user/zmt00) (Ping timeout: 276 seconds) |
| 2024-11-01 11:18:30 +0100 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) |
| 2024-11-01 11:16:45 +0100 | ubert | (~Thunderbi@178.115.51.39.wireless.dyn.drei.com) (Ping timeout: 252 seconds) |
| 2024-11-01 11:16:19 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) lxsameer |
| 2024-11-01 11:16:18 +0100 | swamp_ | (~zmt00@user/zmt00) (Ping timeout: 248 seconds) |
| 2024-11-01 11:15:22 +0100 | zmt01 | (~zmt00@user/zmt00) zmt00 |
| 2024-11-01 11:14:14 +0100 | zmt00 | (~zmt00@user/zmt00) zmt00 |