| --- Log opened Sat Jul 04 00:00:17 2020 |
| 00:15 | | Kindamoody is now known as Kindamoody[zZz] |
| 00:25 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 00:44 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 00:44 | | mode/#code [+o Kindamoody[zZz]] by ChanServ |
| 00:50 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 00:55 | <~Vornicus> | codewars needs better... uh... I click the "submit" button and it doesn't look like it did anything because the only feedback you get is the replacement of the text in the footer of your editor. |
| 00:57 | <&McMartin> | That's odd. I'm used to it jumping to a completely different page. |
| 00:57 | <&McMartin> | Some kind of script blocking? |
| 00:57 | <&McMartin> | "Attempt" should also be altering the whole left pane. |
| 00:59 | <~Vornicus> | It takes a while to do it is the thing |
| 01:00 | <~Vornicus> | So like you get very basic feedback - that something's happening -- only in the sense that that thing changes, but it takes several seconds and it doesn't even like ... have the button react |
| 01:01 | <~Vornicus> | So the only way I can tell I did it is not in the place where I did it |
| 01:54 | <&McMartin> | I'm going and revisiting stuff I already solved to do resolves in languages that have very different design strategies |
| 01:54 | <&McMartin> | This is dumb and free for the early stuff but the later stuff is rather more interesting |
| 01:55 | | * Vornicus finally gets to one that's vaguely challenging, change making. |
| 01:57 | <&ToxicFrog> | jerith: spellcast in the browser. |
| 02:02 | <&McMartin> | I suppose the most aggressive way of doing this would be going Full Websockets, but meh |
| 02:05 | | * McMartin looks at this C-based AST code. |
| 02:05 | <&McMartin> | ... yep, lessons from Rust are Paying Off here |
| 02:17 | <~Vornicus> | suppose I'm doing this the hard way, the problem's limits make it much shorter than actually getting the proper engineering going. |
| 02:32 | <&ToxicFrog> | McMartin: yeah, an earlier design called for a websocket to each client using core.async to pass messages back and forth |
| 02:33 | <&ToxicFrog> | That does have the advantage that it can more quickly detect player disconnects, but as a practical matter it's not really "disconnect" I care about but "game is blocked on player and player hasn't entered any actions for N minutes" |
| 02:34 | <&ToxicFrog> | So, this approach instead, where the server receives events via POST which update the game-state atom, and the client reads game information with GET which sets a watch on the game-state and then blocks the thread until the state changes in a way that's relevant to the data being requested |
| 02:39 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed] |
| 02:44 | | Degi [Degi@Nightstar-nn5u83.dyn.telefonica.de] has quit [Ping timeout: 121 seconds] |
| 02:54 | | Degi [Degi@Nightstar-tvche1.dyn.telefonica.de] has joined #code |
| 02:59 | | * McMartin nods |
| 04:46 | | Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has joined #code |
| 04:47 | | Pink` [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Ping timeout: 121 seconds] |
| 04:48 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 04:48 | | mode/#code [+o Kindamoody[zZz]] by ChanServ |
| 04:52 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 06:22 | | Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Ping timeout: 121 seconds] |
| 06:42 | | Vorntastic [uid293981@Nightstar-ks9.9ff.184.192.IP] has joined #code |
| 06:42 | | mode/#code [+qo Vorntastic Vorntastic] by ChanServ |
| 08:49 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 08:49 | | mode/#code [+o Kindamoody[zZz]] by ChanServ |
| 08:54 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 09:00 | <&jerith> | Vorntastic: If you haven't looked into Julia yet, you might want to. In particular, its syntax allows writing "x*2y^3z" instead of "x * ((2 * y) ^ (3 * z))". |
| 09:01 | <~Vorntastic> | Augh what the hell |
| 09:01 | <~Vorntastic> | No, do not |
| 09:01 | <&jerith> | Oops, I messed up the parens. "x * 2 * (y ^ (3 * x))" |
| 09:02 | <&jerith> | So that's actually the same as "2x * y^3z". |
| 09:04 | <&jerith> | This also gives them complex numbers "for free" merely by defining a constant ("im" because both "i" and "j" are popular index variables) that you append to your literal coefficient. |
| 09:07 | <&jerith> | Literal coefficients bind more tightly than "*" or "/", and can be applied to any single variable/constant or paren group. |
| 09:08 | <&jerith> | So "2x/3y" is equivalent to "(2 * x) / (3 * y)". |
| 09:09 | <&jerith> | Anyway, the docs have a bunch of examples demonstrating how that makes a lot of stuff much clearer and easier to read. |
| 09:10 | <&jerith> | I also has √ as a unary operator. ^.^ |
| 09:11 | <&jerith> | *It |
| 09:11 | < catalyst> | you does? |
| 09:11 | <&jerith> | I does, but only in Julia code. |
| 09:24 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code |
| 09:30 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds] |
| 09:58 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 09:58 | | mode/#code [+o Kindamoody[zZz]] by ChanServ |
| 09:58 | | Kindamoody[zZz] is now known as Kindamoody |
| 10:06 | | catalyst_ [catalyst@Nightstar-lcmvh4.dab.02.net] has joined #code |
| 10:06 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [Connection reset by peer] |
| 10:10 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code |
| 10:10 | | catalyst_ [catalyst@Nightstar-lcmvh4.dab.02.net] has quit [Ping timeout: 121 seconds] |
| 10:29 | <&jerith> | Heh, Julia uses "*" for string concatenation on the basis that "+" is usually commutative but "*" often is not. |
| 10:32 | <~Vorntastic> | Wat |
| 10:33 | <&jerith> | The last bit of https://docs.julialang.org/en/v1/manual/strings/#man-concatenation-1 (just before the "Interpolation" section) explains. |
| 10:43 | <~Vorntastic> | Also if the logo is not a Julia set I will be displeased |
| 10:44 | <~Vorntastic> | It is not, I am displeased |
| 11:01 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 11:04 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code |
| 11:07 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 11:07 | | mode/#code [+o Kindamoody] by ChanServ |
| 11:13 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 11:15 | <&jerith> | Bleh. Codewars uses the obsolete FactCheck library for its Julia test, and their fork seems to work okay on modern Julia except it always reports overall success even when individual tests fail. |
| 11:16 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Connection reset by peer] |
| 11:32 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 11:32 | | mode/#code [+o Kindamoody] by ChanServ |
| 11:39 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 11:57 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code |
| 12:11 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 12:11 | | mode/#code [+o Kindamoody] by ChanServ |
| 15:12 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code |
| 15:12 | | mode/#code [+qo Vornicus Vornicus] by ChanServ |
| 15:33 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 16:05 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 16:05 | | mode/#code [+o Kindamoody] by ChanServ |
| 16:31 | | Vorntastic [uid293981@Nightstar-ks9.9ff.184.192.IP] has quit [[NS] Quit: Connection closed for inactivity] |
| 17:35 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 17:45 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 17:45 | | mode/#code [+o Kindamoody] by ChanServ |
| 17:53 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 17:57 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 17:57 | | mode/#code [+o Kindamoody] by ChanServ |
| 18:24 | | VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed] |
| 18:24 | | VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code |
| 18:24 | | mode/#code [+ao VirusJTG VirusJTG] by ChanServ |
| 18:26 | | Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Connection closed] |
| 18:26 | | Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 18:26 | | mode/#code [+o Kimo|autojoin] by ChanServ |
| 18:51 | | Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 19:25 | | Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 19:25 | | mode/#code [+o Kimo|autojoin] by ChanServ |
| 20:05 | | Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Operation timed out] |
| 20:41 | <&McMartin> | jerith: Ugh. That's a bummer |
| 20:41 | <&McMartin> | And it's an exceptional bummer because their test framework for C - Criterion - is frankly the best I've ever seen for the kinds of uses cases I have when unit testing C |
| 20:48 | <&jerith> | FactCheck seems like a reasonable API (although I have a very small sample size to work from), but it was apparently abandoned in 2017 and the stdlib Test module didn't yet exist then or something. |
| 20:58 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [[NS] Quit: -a- Connection Timed Out] |
| 20:58 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code |
| 21:30 | | VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed] |
| 21:32 | | VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code |
| 21:32 | | mode/#code [+ao VirusJTG VirusJTG] by ChanServ |
| 21:57 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [Connection closed] |
| 21:58 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code |
| 22:07 | < catalyst> | string concatenation shouldn't use + or * imo x) |
| 22:07 | < catalyst> | maybe ++ |
| 22:15 | <~Vornicus> | Lua's .. feels fine to me |
| 22:27 | <&McMartin> | A few BASIC dialects use & |
| 22:29 | <~Vornicus> | Excel does too |
| 22:29 | <&jerith> | BITWISE AND |
| 22:29 | <~Vornicus> | ^ |
| 22:30 | <&jerith> | BITWISE XOR |
| 22:30 | <&[R]> | . isn't a good string concat operator either |
| 22:30 | <~Vornicus> | <3 |
| 22:30 | <~Vornicus> | no, . isn't. .. seems to be fine though |
| 22:31 | <&[R]> | xs' ^ is a bit weird (but it's also a concat operator, instead of simply being a string concat operator) |
| 22:48 | < ErikMesoy> | considering how some languages have += maybe string concatenation could use ,= |
| 22:49 | <&[R]> | , is its own operator in most languages though |
| 22:49 | | Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 22:49 | | mode/#code [+o Kimo|autojoin] by ChanServ |
| 22:51 | < ErikMesoy> | + is also a separate operator in some languages with += |
| 22:51 | < ErikMesoy> | The more I think about it the more I like ,= as an absolutely horrible compromise operator for string concatenation that nobody will like :P |
| 22:51 | <&[R]> | Fair enough |
| 22:52 | <&[R]> | Let's use @ |
| 23:00 | <@TheWatcher> | Nono, \ |
| 23:01 | <~Vornicus> | heck |
| 23:01 | <@TheWatcher> | Or maybe : |
| 23:01 | <~Vornicus> | the macos classic path separator? |
| 23:04 | <@Tamber> | nah, let's use & |
| 23:04 | <@Tamber> | Get back to our roots~ |
| 23:10 | <&McMartin> | I propose <-> |
| 23:13 | <@TheWatcher> | Hm, bit close to the tie-fighter operator for me, but okay |
| 23:14 | <&McMartin> | The problem with the otherwise superior -><- is that you have to worry about it being confused for ->< followed by a unary minus. |
| 23:15 | <@TheWatcher> | (Hail Eris) |
| 23:15 | <&McMartin> | I forget what the tie-fighter operator is actually for. <> is an old !=. |
| 23:15 | <&McMartin> | But Tie Fighter is <=>, right? |
| 23:18 | <@TheWatcher> | Yeah, it's a numeric three-way comparison - returns -1, 0, or 1 for lhs < rhs, lhs=rhs, lhs > rhs. |
| 23:28 | <&McMartin> | The Kirby operator \(^.^)/ |
| 23:31 | | KiMo|autorejoin [Kindamoody@Nightstar-j22gb7.mobileonline.telia.com] has joined #code |
| 23:31 | | mode/#code [+o KiMo|autorejoin] by ChanServ |
| 23:31 | | KiMo|autorejoin is now known as Kindamoody |
| 23:32 | <@Tamber> | Surely the Tie Fighter op should be |=| ? |
| 23:33 | | Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 23:37 | <~Vornicus> | yeah that's clearly a tie interceptor |
| 23:45 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds] |
| 23:46 | | macdjord [macdjord@Nightstar-rslo4b.mc.videotron.ca] has quit [Connection closed] |
| 23:51 | | macdjord [macdjord@Nightstar-rslo4b.mc.videotron.ca] has joined #code |
| 23:51 | | mode/#code [+o macdjord] by ChanServ |
| --- Log closed Sun Jul 05 00:00:19 2020 |