00:35 <sleeplessy> is it ok to translating ponylang documents into other languages?

01:01 <jemc> sleeplessy: it's a good question - we certainly have no problem with you working on translations of documentation, but it's hard for it to become an official documentation set when changes come in, unless we have someone who can update the documentation on hand at all times (which probably isn't feasible for a volunteer-run project)

01:02 <jemc> it looks like the Rust-lang approach is to let community members do unofficial translations, and link to them from the official docs

01:02 <sleeplessy> emm,but actually there're not much translations i found

01:02 <sleeplessy> especially in my language

01:02 <jemc> with those community members being responsible for keeping up to date with changes

01:02 <sleeplessy> i couldnt find any -- even a blog of the little pony

01:02 <jemc> sleeplessy: yeah, it looks like they have Russian, Korean, Chinese, & Spanish

01:04 <sleeplessy> actually, no chinese translations,even some introduction

01:04 <sleeplessy> there should be some,but i google it and find,nobody tyies to give ponylang a try or introduce it to others in my country

01:05 <jemc> I saw this Chinese Rust book they linked to, but I don't read Chinese so I can't confirm the extent/quality of the docs: https://github.com/KaiserY/rust-book-chinese

01:05 <jemc> linked to from here: https://doc.rust-lang.org/1.2.0/#community-translations

01:05 <sleeplessy> the rust one is just ok

01:06 <sleeplessy> there are lots of rust programmers in china thanks to the document

01:07 <jemc> I think Pony would probably want to take the same approach that rust took - let you run the translation project, and link to it from the official docs

01:07 <sleeplessy> while ponylang is still in prelease,it would be a problem keeping update with the official one

01:08 <sleeplessy> best solution is have a community group but there should be a first one to let others know,and learn ponylang

01:12 <SeanTAllen> sleeplessy: we'd be open to translations as long as someone was responsible for updating them. are you interested in doing a translation and maintaining it?

01:13 <sleeplessy> i have the interests,and i do want to translate it... , SeanTAllen

01:14 <sleeplessy> but im not sure how many contributors can i gather

01:14 <SeanTAllen> awesome. you'd have our support as long as we can work out maintenance.

01:14 <SeanTAllen> well, sleeplessy, it all starts with 1 person and goes from there.

01:14 <SeanTAllen> if you want to take it on, let us know and we can figure out how to make maintenance as easy as possible.

01:15 <sleeplessy> okay, i would start it as quick as i can

01:17 <SeanTAllen> thank you sleeplessy. let us know what assistance you need. we're a volunteer project but will do the best we can!

01:17 <sleeplessy> thanks

01:19 <sleeplessy> anyway, i guess it would be better to have a translated version of the Discover page

01:19 <sleeplessy> or a link...whatever

01:23 <ruby_> hi

01:31 <jemc> ruby_: hi, and welcome!

01:33 <SeanTAllen> hi ruby_ ! welcome.

01:34 <SeanTAllen> are you codenoid from GH ruby_ ?

01:34 <ruby_> Yup, ^^

01:35 <SeanTAllen> i'll end up forgetting that. i'm not good with keeping different usernames in sync. but, i'm giving myself points for noticing.

01:39 <codenoid> Sorry for that, I'm really new in Xchat, haha :+1:

01:39 <SeanTAllen> o nice. now i can keep it straight in my head

04:22 <hobomatic> the capability specification between 'fun' and a given method name applies to the receiver, right?

04:26 <hobomatic> so, for instance, something like `primitive foo; fun tag x(): UINT64 => 0` is saying that within the body of the method x, no actual reading/writing of object-local state is possible?

04:34 <hobomatic> i guess that doesn't even make sense for primitives, but ignoring that detail

12:30 <SeanTAllen> hobomatic: correct, tag means its opaque, no read or write of object local state can occur has part of that call