#perl6-dev on 1 September 2018 - Raku Programming Language Log

Perl 6 language and compiler development | Logs at colabti.org/irclogger/irclogger_log/perl6-dev | For toolchain/installation stuff see #perl6-toolchain | For MoarVM see #moarvm
Set by Zoffix on 27 July 2018.

tbrowder_

can't these jerks be prosecuted?

00:22

00:22 stmuk_ left

geekosaur

you have to find them. and most of these are from "mules", not directly involved and tracking down how they got infected will be tricky

00:23

and many of them from other countries, and many of those don't have agreements with other countries' law enforcement and often don't have the ability to track them down

00:24

(or the willingness, hello russia)

00:25 stmuk_ joined, p6bannerbot sets mode: +v stmuk_ 00:28 epony left 00:48 fake_space_whale joined 00:49 p6bannerbot sets mode: +v fake_space_whale 01:05 stmuk joined 01:06 p6bannerbot sets mode: +v stmuk 01:07 stmuk_ left 02:25 aaron7 joined 02:26 aaron7 left 03:33 tyil left 03:38 Louis17 joined 03:39 Louis17 left 03:40 tyil joined, p6bannerbot sets mode: +v tyil 05:51 fake_space_whale left 05:53 jesse23 joined 05:57 jesse23 left 05:59 reportable6 joined, p6bannerbot sets mode: +v reportable6 06:25 Zapy3 joined 06:28 Zapy3 left 07:45 dct joined, p6bannerbot sets mode: +v dct 08:19 dct left, dct joined, p6bannerbot sets mode: +v dct 08:27 dct left 09:41 robertle joined 09:42 p6bannerbot sets mode: +v robertle 09:55 matti1 joined 09:58 matti1 left

nine

Another fun fact about explicitly-manage: if you apply it to a string constant like explicitly-manage('foo'), then this will apply to all equal string constants. So a later this-function-wont-free-the-string('foo') will in fact leak the C string.

10:01

10:04 ilmari_ left, AlexDaniel` left, tyil[m] left, CIAvash[m] left 10:06 yoleaux left 10:12 CIAvash[m] joined, p6bannerbot sets mode: +v CIAvash[m], pmurias joined 10:13 p6bannerbot sets mode: +v pmurias 10:30 AlexDaniel` joined, ilmari_ joined, tyil[m] joined, p6bannerbot sets mode: +v ilmari_, p6bannerbot sets mode: +v AlexDaniel`, p6bannerbot sets mode: +v tyil[m]

nine

I dare say, even for the case of a native function that expects a string to survive the call yet still requires the user to actually free it, requiring the argument to be marked explicitly-managed seems to be the sane option.

11:01

The fact that the string needs to be kept longer than the function call is still a static property of that function.

11:03

The current explicitly-manage() is not even suitable for that use case, because while the CStr repr does keep a UTF-8 encoded C string around and this is even free()'d on GC, that's not actually the string that gets passed to the native function.

11:19

We still encode a new string for that on every call.

11:33 MasterDuke left

pmurias

nine: wouldn't exposing the ability to manually alloc/free something in Perl 6 land solve all the problems with weird memory mangagement schemes?

11:40

timotimo

"is memory-managed(alloc => -> $size { Buf.allocate($size) }, free => -> { })"

pmurias

the docs for explicitly-manage: docs.perl6.org/routine/explicitly-manage

11:43

don't really explain what it does

11:45 jdv79 left 11:46 jdv79 joined, p6bannerbot sets mode: +v jdv79

nine

The actual solution is so simple, it really hurts...

11:47

If the string needs to survive the call but still be free'd by Perl 6 or if you really want the same pointer to be passed to several function calls, just encode it to a blob explicitly and use utf8 as type in the native sub instead of STr

11:48

There's really no need for explicitly-manage()

11:50 epony joined, p6bannerbot sets mode: +v epony

nine

sub SetString(utf8) is native('./02-simple-args') { * }; my $str = 'foo'.encode; SetString($str); CheckString($str); # works just fine

11:50

This also makes it much harder to misuse the sub. Type checks will keep you from passing normal strings and I don't think anyone would erroneously assume SetString($str.encode); CheckString($str.encode); would result in both calls getting the same pointer.

11:53

11:55 ephemer0l_29 joined, ephemer0l_29 left

nine

Ok, there's still one use case that's not covered there: take-some-string($str); take-same-string-and-also-free-it($str);