Newest at the top
| 2024-10-25 21:24:39 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2024-10-25 21:19:41 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-25 21:12:25 +0200 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod |
| 2024-10-25 21:11:24 +0200 | down200 | (~down200@shell.lug.mtu.edu) down200 |
| 2024-10-25 21:11:04 +0200 | briandaed | (~root@185.234.210.211.r.toneticgroup.pl) (Remote host closed the connection) |
| 2024-10-25 21:10:56 +0200 | alexherbo2 | (~alexherbo@2a02-8440-3204-088a-fce6-8c1c-cc30-bfac.rev.sfr.net) (Remote host closed the connection) |
| 2024-10-25 21:09:27 +0200 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) (Remote host closed the connection) |
| 2024-10-25 21:08:28 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-10-25 21:07:23 +0200 | down200 | (~down200@shell.lug.mtu.edu) (Quit: ZNC - https://znc.in) |
| 2024-10-25 21:01:38 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-25 21:00:44 +0200 | caconym | (~caconym@user/caconym) caconym |
| 2024-10-25 21:00:05 +0200 | caconym | (~caconym@user/caconym) (Quit: bye) |
| 2024-10-25 20:55:32 +0200 | Digit | (~user@user/digit) Digit |
| 2024-10-25 20:51:19 +0200 | EvanR | (~EvanR@user/evanr) (Ping timeout: 260 seconds) |
| 2024-10-25 20:50:36 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-10-25 20:50:27 +0200 | <dolio> | Is it actually based on that? |
| 2024-10-25 20:49:33 +0200 | mceresa | (~mceresa@user/mceresa) (Ping timeout: 245 seconds) |
| 2024-10-25 20:49:00 +0200 | Smiles | (uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2024-10-25 20:46:15 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-25 20:45:16 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2024-10-25 20:41:58 +0200 | mauke | throws an ArrayStoreException |
| 2024-10-25 20:41:27 +0200 | <EvanR> | Java is the best dynamically typed language |
| 2024-10-25 20:41:14 +0200 | <EvanR> | the dynamically typed hierarchy |
| 2024-10-25 20:41:03 +0200 | <EvanR> | ok, that's what I figured |
| 2024-10-25 20:39:15 +0200 | <briandaed> | "This may be surprising, but the Haskell exception system is modeled off of Java-style Object Oriented inheritance (shocking, I know)." source: https://tech.fpcomplete.com/haskell/tutorial/exceptions/ |
| 2024-10-25 20:36:50 +0200 | <mauke> | the original one or the extensible exception hierarchy thing? |
| 2024-10-25 20:35:44 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds) |
| 2024-10-25 20:35:35 +0200 | <EvanR> | where did the haskell exception system come from. Is it "original research" or based on a previous language's exception system |
| 2024-10-25 20:33:06 +0200 | <lxsameer> | EvanR: tomsmeding mauke thanks for the help folks |
| 2024-10-25 20:32:51 +0200 | <lxsameer> | tomsmeding: cheers |
| 2024-10-25 20:32:41 +0200 | <tomsmeding> | (read the haddocks) |
| 2024-10-25 20:32:40 +0200 | <lxsameer> | tomsmeding: yes |
| 2024-10-25 20:32:34 +0200 | <tomsmeding> | Control.Exception.catch |
| 2024-10-25 20:32:19 +0200 | <tomsmeding> | no need to have another field for this in the record, as far as I can see |
| 2024-10-25 20:32:14 +0200 | scaniatrucker | (~user@78.56.98.5) (Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.4)) |
| 2024-10-25 20:32:10 +0200 | <tomsmeding> | inside the implementation of the DB methods |
| 2024-10-25 20:32:02 +0200 | <tomsmeding> | lxsameer: okay; then "will handle any uncaught error using an error handler" is just something that it can do, right? |
| 2024-10-25 20:31:37 +0200 | <lxsameer> | tomsmeding: it is any code that implement the methods of the DB type |
| 2024-10-25 20:31:22 +0200 | <tomsmeding> | mauke: good point! |
| 2024-10-25 20:31:14 +0200 | <tomsmeding> | because then, can't it "just" catch them? |
| 2024-10-25 20:31:02 +0200 | <tomsmeding> | lxsameer: what is a "backend"? Is that one of the functions in that DB record? |
| 2024-10-25 20:30:40 +0200 | <mauke> | because SomeException is also an instance of Exception, so if your e is already SomeException, you might accidentally double-wrap it |
| 2024-10-25 20:30:16 +0200 | <lxsameer> | tomsmeding: the backend will throw them. and in my head the backend will handle any uncaught error using a error handler and re-throw those that it doesn't know about |
| 2024-10-25 20:30:15 +0200 | morsinichi | (~morsinich@61.4.97.157) (Remote host closed the connection) |
| 2024-10-25 20:30:10 +0200 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2024-10-25 20:30:05 +0200 | <mauke> | using the SomeException data constructor directly is probably a mistake in general. toException is the way to go |
| 2024-10-25 20:29:30 +0200 | <tomsmeding> | agree |
| 2024-10-25 20:29:23 +0200 | <EvanR> | letting someone catch it if they want |
| 2024-10-25 20:28:59 +0200 | Igloo | (~ian@81.2.99.210) |
| 2024-10-25 20:28:49 +0200 | <EvanR> | by returning IO exception* |