Newest at the top
| 2025-03-17 18:07:46 +0100 | euleritian | (~euleritia@95.90.214.149) |
| 2025-03-17 18:07:31 +0100 | <ski> | yes |
| 2025-03-17 18:07:19 +0100 | <ski> | it's correct that you can't just replace `foo' by its definition in `(bar foo)', if `bar' is a macro, which could lead one to want to use e.g. a different bracket syntax for special forms and macro invokations, than for procedure calls |
| 2025-03-17 18:07:09 +0100 | <mauke> | in a lisp-6 like perl, sub list($list, @list) { my %list = map +($_ => $list), @list; \%list } is perfectly cromulent code |
| 2025-03-17 18:07:03 +0100 | euleritian | (~euleritia@95.90.214.149) (Read error: Connection reset by peer) |
| 2025-03-17 18:05:45 +0100 | euphores | (~SASL_euph@user/euphores) euphores |
| 2025-03-17 18:05:09 +0100 | <ski> | even without macros, things tend to need to be interpreted in context. `(a,b)' in an expression context, means something else than in a type context. in one context `Foo' could be a module, while in another it could be a type constructor, or a data constructor in yet another. in Lisp-2's, like Common Lisp, `(lambda (list) (list list))' is a procedure constructing a singleton list from its input argument |
| 2025-03-17 18:04:10 +0100 | euleritian | (~euleritia@95.90.214.149) |
| 2025-03-17 18:03:56 +0100 | jespada | (~jespada@2800:a4:22cd:2500:4d25:68ba:28dd:cc11) jespada |
| 2025-03-17 18:03:52 +0100 | euleritian | (~euleritia@dynamic-176-006-138-112.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2025-03-17 18:02:17 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod |
| 2025-03-17 18:01:44 +0100 | <EvanR> | "let over lambda" my ass |
| 2025-03-17 18:01:29 +0100 | target_i | (~target_i@user/target-i/x-6023099) target_i |
| 2025-03-17 18:01:25 +0100 | <EvanR> | but it's a lisp weenie! |
| 2025-03-17 18:01:16 +0100 | <EvanR> | what a bait and switch, I thought it was going to rail against lisp |
| 2025-03-17 18:00:38 +0100 | <mauke> | "Any language that uses infix syntax is reducing the possibilities of its abstractions in many ways." ... yeah, call me when common lisp supports ((f x) y) |
| 2025-03-17 18:00:37 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 248 seconds) |
| 2025-03-17 18:00:33 +0100 | <ski> | only the first section has that title. the next is about something else |
| 2025-03-17 17:59:49 +0100 | <EvanR> | I read the first chapter and thought it was end of it. But it's that my monitor cuts off the monofilament scrollbar UI on the right |
| 2025-03-17 17:57:19 +0100 | euphores | (~SASL_euph@user/euphores) (Ping timeout: 260 seconds) |
| 2025-03-17 17:56:24 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-17 17:55:13 +0100 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh |
| 2025-03-17 17:55:00 +0100 | <ski> | not entirely convinced by the macro argument, either |
| 2025-03-17 17:54:58 +0100 | <mauke> | ¹) well, some restrictions. but you can arbitrarily nest statements and expressions inside each other |
| 2025-03-17 17:54:28 +0100 | <ski> | yes |
| 2025-03-17 17:54:27 +0100 | <mauke> | for example, perl has both infix operators *and* no¹ restrictions on what you can nest |
| 2025-03-17 17:53:47 +0100 | <mauke> | that article looks a bit confused |
| 2025-03-17 17:49:50 +0100 | ski | . o O ( "Let Over Lambda - Lisp Is Not Functional" <https://letoverlambda.com/index.cl/guest/chap5.html#sec_1> ) |
| 2025-03-17 17:48:32 +0100 | <haskellbridge> | <Bowuigi> Uh isn't that what base64 does? |
| 2025-03-17 17:47:34 +0100 | euphores | (~SASL_euph@user/euphores) euphores |
| 2025-03-17 17:38:45 +0100 | euphores | (~SASL_euph@user/euphores) (Quit: Leaving.) |
| 2025-03-17 17:37:50 +0100 | <EvanR> | but what's the fun in that |
| 2025-03-17 17:37:46 +0100 | <EvanR> | ok we have better ways to do that, using Word32 or V4 Word8 |
| 2025-03-17 17:36:52 +0100 | <EvanR> | and later stitch it back together for output |
| 2025-03-17 17:35:53 +0100 | <EvanR> | but if you wanted to process UTF-8 text without fully decoding it, you could map the 1-4 byte code units to a number and put that number in the Char data, looking like gibberish |
| 2025-03-17 17:35:22 +0100 | acidjnk | (~acidjnk@p200300d6e71c4f06a07cb2b65789c630.dip0.t-ipconnect.de) acidjnk |
| 2025-03-17 17:35:12 +0100 | <EvanR> | the value of a Char is backed by a word, normally can only be used for codepoints |
| 2025-03-17 17:34:33 +0100 | <EvanR> | I just thought of the stupidest idea |
| 2025-03-17 17:32:58 +0100 | kuribas | (~user@ip-188-118-57-242.reverse.destiny.be) (Remote host closed the connection) |
| 2025-03-17 17:30:54 +0100 | acidjnk | (~acidjnk@p200300d6e71c4f06a07cb2b65789c630.dip0.t-ipconnect.de) (Ping timeout: 252 seconds) |
| 2025-03-17 17:30:50 +0100 | jespada | (~jespada@2800:a4:22cd:2500:4d25:68ba:28dd:cc11) (Quit: My Mac has gone to sleep. ZZZzzz…) |
| 2025-03-17 17:28:26 +0100 | <haskellbridge> | <Liamzee> Guessing about his circumstances, I think one possible observation is that if your abstractions are bad, not forcing you into productive natural means of design, you have design patterns, and these can be woefully ad-hoc, experimental, and meaningless. |
| 2025-03-17 17:27:15 +0100 | <haskellbridge> | <Liamzee> also monochrom: I found the guy who hated OOP with a passion, friedbrice on Reddit. |
| 2025-03-17 17:26:40 +0100 | <haskellbridge> | <Liamzee> Axman6: Axman6: ghcide seems an appropriate name. |
| 2025-03-17 17:19:38 +0100 | Googulator | (~Googulato@2a01-036d-0106-4b74-b88c-ff83-9891-e272.pool6.digikabel.hu) |
| 2025-03-17 17:19:24 +0100 | Googulator | (~Googulato@2a01-036d-0106-4b74-b88c-ff83-9891-e272.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-03-17 17:18:14 +0100 | kh0d | (~kh0d@212.200.181.159) (Remote host closed the connection) |
| 2025-03-17 17:16:44 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) lxsameer |
| 2025-03-17 17:16:13 +0100 | alexherbo2 | (~alexherbo@2a02-8440-3605-d6c6-743a-eb13-80f6-c84d.rev.sfr.net) (Remote host closed the connection) |
| 2025-03-17 17:15:30 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 272 seconds) |