17:41 guifa_ joined
guifa_ voldenet timo: thanks. I suppose for now (since it would be a rare exception) I can just throw an MVM_exception and then down the road try to provide better error handling 17:57
Unfortunately I realized I can't catch it in Raku land. hostname resolution is done at the MoarVM level and it's only after that where I can potentially detect conflicting parameters 17:58
timo i'm not sure what that means
guifa_ so the error that I'm looking to catch/handle is when the IPv6 interface passed in mismatches the resolved IPv6 address's interface 17:59
so hypothetically, 'raku.org' might resolve to ab:cd::ef%42 (it's valid in a hosts file). But if a user specifies that hostname of 'raku.org' and an interface of '420', which interface should be used? 42 or 420? 18:00
timo presumably, the name raku.org with the ip %42 wouldn't necessarily be valid for %420 at all, so it must not use that entry? 18:02
but you were going to explain how you're doing it, right? 18:04
guifa_ timo: very potentially. for now, per patrickb, our best bet is to just error if we catch an inconsistency 18:05
I figured it'd be a helpful if we could provide in Raku a helpful error message though, rather than just dying on a VM error. (I highly, highly doubt this situation will come up in real world usage) 18:07
timo well, the message can still be helpful 18:10
the user would just have to string-parse the details out in user code if they really need the individual bits 18:12
guifa_ Yeah, hence me wondering the best way to pass it up. But for now since it's not critical functionality and because I want to finish the project and add in the Raku-level code, I think I'll just throw an MVM exception 18:13
timo yeah
18:22 librasteve_ left 18:53 disbot4 left 18:54 disbot1 joined 18:58 guifa_ left 20:22 guifa_ joined 20:46 guifa_ left 21:18 MasterDuke joined
MasterDuke Voldenet: huh, never knew about MVM_exception_throwobj 21:20
21:21 guifa_ joined 22:08 MasterDuke left 22:14 guifa_ left 22:48 guifa_ joined 22:52 guifa_ left