Minetest logo

IRC log for #minetest, 2024-08-19

| Channels | #minetest index | Today | | Google Search | Plaintext

All times shown according to UTC.

Time Nick Message
00:23 SFENCE joined #minetest
00:42 SFENCE joined #minetest
01:10 SFENCE joined #minetest
01:30 SFENCE joined #minetest
01:49 SFENCE joined #minetest
02:11 SFENCE joined #minetest
02:29 SFENCE joined #minetest
02:49 SFENCE joined #minetest
03:38 YuGiOhJCJ joined #minetest
03:50 SFENCE joined #minetest
04:00 MTDiscord joined #minetest
04:15 Izaya joined #minetest
04:22 Izaya joined #minetest
04:28 SFENCE joined #minetest
04:41 SFENCE joined #minetest
04:48 Trifton joined #minetest
04:59 AwesomeAdam54321 joined #minetest
05:11 SFENCE joined #minetest
05:42 SFENCE joined #minetest
06:02 gregon joined #minetest
06:59 gregon joined #minetest
07:18 MinetestBot [git] sfan5 -> minetest/minetest: [no sq] Move shaders & remove dead Irrlicht tests (#15006) b010714 https://github.com/minetest/minetest/commit/b0107144261f6513bbde95323c9663a71ed8f3c9 (2024-08-19T07:17:52Z)
07:30 cheek_pain joined #minetest
07:56 bodiccea_ joined #minetest
08:04 Hanicef joined #minetest
08:09 bodiccea joined #minetest
09:57 ireallyhateirc joined #minetest
10:06 gregon joined #minetest
10:37 gh00p joined #minetest
10:54 Glaedr joined #minetest
11:08 boingman joined #minetest
11:23 TomTom joined #minetest
13:11 jaca122 joined #minetest
13:26 gh00p joined #minetest
13:31 silverwolf73828_ joined #minetest
13:32 silverwolf73828 joined #minetest
13:56 bodiccea joined #minetest
14:49 Izaya left #minetest
14:49 Izaya joined #minetest
14:54 Izaya left #minetest
14:56 Izaya joined #minetest
15:02 amfl joined #minetest
15:37 cation joined #minetest
16:03 jaca122 joined #minetest
16:17 MiniontobyPI joined #minetest
16:34 Talkless joined #minetest
16:38 bodiccea joined #minetest
16:50 gregon joined #minetest
17:06 bodiccea joined #minetest
17:14 mrkubax10 joined #minetest
17:21 kamdard joined #minetest
17:47 mrkubax10 joined #minetest
17:49 Minigun_125 joined #minetest
18:25 wiresoup joined #minetest
18:26 gh00p joined #minetest
18:43 Izaya joined #minetest
18:43 Verticen joined #minetest
18:54 Izaya joined #minetest
19:03 Izaya left #minetest
19:13 mrkubax10 joined #minetest
19:13 jaca122 joined #minetest
19:15 Izaya joined #minetest
19:30 Izaya joined #minetest
19:43 YuGiOhJCJ joined #minetest
19:54 zleap left #minetest
20:03 Izaya joined #minetest
20:09 Desour joined #minetest
20:29 Izaya joined #minetest
20:58 Izaya joined #minetest
21:14 Izaya joined #minetest
21:25 Izaya joined #minetest
21:37 sparky4 joined #minetest
21:44 bodiccea joined #minetest
22:36 panwolfram joined #minetest
23:07 Eragon_ joined #minetest
23:28 Zambyte` joined #minetest
23:39 vampirefrog joined #minetest
23:40 ireallyhateirc Is there a discount "dump" that will only dump limited info?
23:41 ireallyhateirc or maybe what's the good practice for errors when a wrong argument is passed to a function?
23:42 ireallyhateirc I have pretty fat objects with tangled/circular references and printing them can stuck Minetest for long
23:46 MTDiscord <luatic> dump is not optimized
23:47 MTDiscord <luatic> such pretty printing is usually intended for debugging, i wouldn't do that as part of error messages. keep those simple and to the point, when the error arises, the debugging programmer can insert printf debugging or use other debugging tools as they please.
23:48 ireallyhateirc Ok so just "argument 'a' has type 'function' but 'number' expected" ?
23:49 MTDiscord <warr1024> you could always try another format like json or minetest.serialize, and just add the prettiness in post-processing after you find the messages in your logs
23:50 ireallyhateirc my objects are huge. Like a linked list of 100 points huge, where each point also has the path object linked
23:50 MTDiscord <luatic> ireallyhateirc: if you want that level of granularity, sure. but often littering everything with type checks in a duck-typed language is overkill and a waste of time tbh.
23:51 ireallyhateirc I add type checks into object constructors usually
23:52 ireallyhateirc that way I catch errors early, instead of later in some unrelated code
23:52 ireallyhateirc Also some errors tell users they did a stupid thing and should not do that
23:55 MTDiscord <luatic> To an extent type checks can be helpful, especially if the data flow isn't clear, or if you want to be especially helpful towards your users. Just don't litter your code with them. And if you really want types generally, maybe look into statically type checking Lua preprocessors.

| Channels | #minetest index | Today | | Google Search | Plaintext