2025/01/09

Newest at the top

2025-01-09 13:04:12 +0100yin(~z@user/zero) (Read error: Connection reset by peer)
2025-01-09 13:03:50 +0100hseg(~gesh@46.120.21.249)
2025-01-09 13:02:17 +0100caconym(~caconym@user/caconym) caconym
2025-01-09 13:01:06 +0100__monty__(~toonn@user/toonn) toonn
2025-01-09 13:00:04 +0100caconym(~caconym@user/caconym) (Quit: bye)
2025-01-09 12:59:36 +0100euphores(~SASL_euph@user/euphores) euphores
2025-01-09 12:58:13 +0100forell(~forell@user/forell) (Ping timeout: 248 seconds)
2025-01-09 12:57:43 +0100lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) lortabac
2025-01-09 12:50:02 +0100__monty__(~toonn@user/toonn) (Ping timeout: 252 seconds)
2025-01-09 12:49:55 +0100euphores(~SASL_euph@user/euphores) (Read error: Connection reset by peer)
2025-01-09 12:44:19 +0100alexherbo2(~alexherbo@2a02-8440-e505-36d8-e9e7-2f9d-7370-79e4.rev.sfr.net) (Remote host closed the connection)
2025-01-09 12:41:10 +0100merijn(~merijn@77.242.116.146) merijn
2025-01-09 12:33:45 +0100alexherbo2(~alexherbo@2a02-8440-e505-36d8-e9e7-2f9d-7370-79e4.rev.sfr.net) alexherbo2
2025-01-09 12:29:40 +0100alexherbo2(~alexherbo@2a02-8440-e505-36d8-e9e7-2f9d-7370-79e4.rev.sfr.net) (Ping timeout: 240 seconds)
2025-01-09 12:21:41 +0100xff0x(~xff0x@2405:6580:b080:900:f740:949c:e296:8382)
2025-01-09 12:16:29 +0100comerijn(~merijn@77.242.116.146) (Ping timeout: 272 seconds)
2025-01-09 12:14:30 +0100 <haskellbridge> <hellwolf> okay, you guys convinced me that I should shove "divMod" "quotRem" to people's throat.
2025-01-09 12:13:40 +0100 <[exa]> (and many other languages are sufficiently lucky to have inherited the // comments from C to avoid this issue. :D)
2025-01-09 12:13:14 +0100traxex(traxex@user/traxex) traxex
2025-01-09 12:13:00 +0100 <[exa]> hellwolf: in julia the // is the rational %
2025-01-09 12:08:59 +0100CiaoSen(~Jura@46.167.29.227) (Ping timeout: 265 seconds)
2025-01-09 12:05:11 +0100 <hellwolf> in python, it is `div`
2025-01-09 12:04:56 +0100 <hellwolf> one for div one for quot
2025-01-09 12:04:50 +0100 <hellwolf> not a good start :)
2025-01-09 12:04:47 +0100 <hellwolf> I already find two semantics for "//" in two different languages
2025-01-09 12:03:50 +0100 <__monty__> The lack of operators encouraging the use of divMod and quotRem is actually kind of a feature.
2025-01-09 12:00:45 +0100 <enikar> :)
2025-01-09 11:59:57 +0100 <hellwolf> A cut and smart parrot is a parrot, after all.
2025-01-09 11:59:24 +0100 <enikar> indeed ;)
2025-01-09 11:58:39 +0100 <hellwolf> I should stop using gpt for serious stuff.
2025-01-09 11:58:31 +0100 <hellwolf> No, Java does not have a "//" operator for integer division. It uses the single "/" operator for both integer and floating point division. The type of division it performs (integer or floating point) depends on the types of the operands. If both operands are integers, it will perform integer division. If either or both operands are floating points, it will perform floating point division.
2025-01-09 11:58:31 +0100 <hellwolf> nix-shell$ echo "Does Java not have // integer division operator, with two slashes" | chatgpt
2025-01-09 11:58:23 +0100 <lambdabot> <hint>:1:4: error: parse error on input ‘**’
2025-01-09 11:58:22 +0100 <hellwolf> > 2. **Integer or Floor Division**: Denoted by "//" in Python and Java 8 onwards, '%' in Swift or the `div` function in Pascal. This operator rounds the result down to the nearest whole number. For example, in Python, 5//2 will result in 2.
2025-01-09 11:57:35 +0100 <hellwolf> ya... :D
2025-01-09 11:57:23 +0100 <__monty__> Isn't that a line comment in Java?
2025-01-09 11:57:02 +0100 <__monty__> Alternatively, if you don't want to define them for yourself, you could add conceals (or whatever your editor calls them) for `div` et al. if you think it reads better or whatever.
2025-01-09 11:57:01 +0100 <hellwolf> am I being scammed by ChatGPT?
2025-01-09 11:55:49 +0100 <orangeFlu> Java does not have // afaik
2025-01-09 11:55:09 +0100byorgey(~byorgey@user/byorgey) byorgey
2025-01-09 11:55:02 +0100byorgey(~byorgey@user/byorgey) (Ping timeout: 252 seconds)
2025-01-09 11:54:14 +0100pie_(~pie_bnc@user/pie/x-2818909) __
2025-01-09 11:53:56 +0100pie_(~pie_bnc@user/pie/x-2818909) (Ping timeout: 252 seconds)
2025-01-09 11:49:57 +0100mud(~mud@user/kadoban) (Read error: Connection reset by peer)
2025-01-09 11:49:35 +0100 <hellwolf> could be an option.
2025-01-09 11:49:23 +0100 <mari-estel> maybe they do not need to become operators
2025-01-09 11:49:16 +0100 <hellwolf> //- ?
2025-01-09 11:49:05 +0100kadobanana(~mud@user/kadoban) kadoban
2025-01-09 11:48:58 +0100 <hellwolf> I know, but I dont' know what better variant to use.
2025-01-09 11:48:58 +0100 <hellwolf> 01-09 12:48 <mari-estel> hm _ conventionally means "discard returned"