09:43 <razzy> Good day i wish to all!

10:31 <Regenaxer> Hi razzy!

12:32 <v_m_v> Does anyone have exp. with PicoLisp and Rust? I know that I can use C/C++ but with Rust it also should be possible right?

12:36 <Regenaxer> I have no experience with Rust. In which way can it be called from other programs? As shared libraries, command line, or something else?

12:44 <v_m_v> @Regenaxer: dylibs

12:48 <v_m_v> So I can compile it to so files

12:48 <Regenaxer> Great

12:49 <Regenaxer> So it has a C-interface?

12:51 <v_m_v> It looks like ....yes. You can use Ruby's FFI lib ...Node FFI lib..and Python FFI lib for that.

12:51 <v_m_v> https://doc.rust-lang.org/1.5.0/book/rust-inside-other-languages.html

12:53 <Regenaxer> It is easy in Pil to call a function with a C signature in a shared library

12:54 <v_m_v> It would be so cool to use Rust libs so easy

13:16 <aw-> v_m_v:i have one on github

13:16 <aw-> Rust and Picolisp

13:17 <Regenaxer> Hi aw-! Cool!

13:17 <aw-> https://github.com/aw/picolisp-rust

13:17 <aw-> and also https://github.com/aw/pilrust

13:18 <aw-> it's relatively easy to interface with Rust through PicoLisp, and vice-versa

13:19 <aw-> however some of Rust's types are architecture dependent, so for example, your results can vary between x86 and arm64

13:22 <aw-> (this is from memory, havent messed with Rust+PicoLisp in a year)

13:23 <v_m_v> Ok I have tested...it is working. It is the easiest thing with FFI which I have saw in my life.

13:23 <aw-> v_m_v: well then you haven't tried Zig yet ;)

13:24 <aw-> Zig+PicoLisp is 1000x easier

13:24 <aw-> and also 1000x less code

13:24 <v_m_v> I have heard about it. The only issue which I have with Zig is lack of package manager :(

13:24 <aw-> oh Zig has many other problems too.. like it's not even v1 yet, so still unstable and not production-ready

13:25 <aw-> but so far it's quite a pleasure to code in compared to Rust

13:26 <aw-> v_m_v: feel free to copy/reuse my code examples however you want, no attribution necessary since it's really just example code. Perhaps I'll update the LICENSE.

13:26 <v_m_v> @aw- I've saw that you have used struct with c types. What about Rust types?

13:27 <aw-> v_m_v: yes it's just an example, I have one array using Rust type: [u8; 8]

13:28 <aw-> in picolisp it's extracted as 8 bytes: (B . 8)

13:29 <v_m_v> Amazing. I am working with blockchains each day....Rust security is awesome ..but it is not the best language for data processing. Combined with PicoLisp it woud give me the flexibility.

13:33 <aw-> ok great

13:33 <aw-> I just published a change to those 2 repos

13:33 <aw-> the LICENSE is changed to 0BSD license

13:38 <aw-> v_m_v: be careful with FFI and picolisp, if you're doing blockchain stuff you need to make sure the .so file is loaded from an ABSOLUTE path and you might even want to verify the checksum of the file to ensure it hasn't been altered

13:39 <aw-> the user running the picolisp app shouldn't have write access to the .so shared lib either

13:39 <aw-> and you'll need to validate all the inputs and data passing between the two.. vaidate _very_ carefully

13:40 <aw-> validate* very carefully

13:40 <aw-> Rust "security" won't protect you from stupidity

13:42 <v_m_v> :D I know ... I would be more worried about Rust 3rd party deps then PicoLisp. I am using Pure Rust for blockchain but sometimes I need to build some tools around. Validation/ Admin panels, tests...etc.

13:43 <v_m_v> There I need the flexibility... sometimes I would like to test some creazy scenarios or just process ethereum events. With PiL I could just use Rust Ethereum libs and then put all of the eth events into PiL database for later processing.

13:46 <aw-> Regenaxer: hi btw ;)

13:48 <aw-> v_m_v: also you should be aware, Rust types don't translate perfectly to C types

13:48 <Regenaxer> :)

13:48 <aw-> that's why in my examples I used c_char and c_long etc

13:50 <v_m_v> Now I would have my websockets in PiL ;) :D

13:54 <aw-> enjoy