I think you misplaced your comment?

Maybe it's a bug, but my false flag alarm bells are ringing loudly here. Although to be fair, they always do that whenever they get a whiff of anything from the modern security theater industry.

Or maybe my mind is wrongly biased towards applying a "Problem - Reaction - Solution" reading to many "commercial" moves.

It sounds interesting but who in the world is going to write article in the abstract wiki? It doesn't seem at all accessible.

Sharing, because I had to look up Abstract Wikipedia

Abstract Wikipedia is an in-development project of the Wikimedia Foundation. It aims to use Wikifunctions to create a language-independent version of Wikipedia using its structured data.

Available on Unix only.

Only kills the thread if it has enabled cancellation

I mean, they will probably set it up correctly to be able to use it

https://docs.rs/stop-thread/latest/stop_thread/fn.kill_thread_graceful.html

In this way, we can avoid relying on subprocesses and instead use threads (or, technically, asynchronous tasks) in Rust. Threads/tasks are much easier to manage

I believe, in their case cancelling a sync operation will not be a problem because they will not forever block on executing user-provided code, but cancelling a synchronous thread is not easy, afaik

No android version :( 99% of what I write is on my phone.

Apparently, Wikifunctions is a place to define e.g. mathematical formulas, so that they can be executed ad-hoc to provide insights about common questions.

Certainly makes sense to run those functions sandboxed in WebAssembly, since the function code is user-provided.
And then, yeah, I can imagine the process management making up a good amount of the complexity of their backend code...

This is cool. I'm testing it out in my Obsidian vault.

To be fair pattern recognition is a pretty decent use of AI. And spelling is pretty much a pattern.

Don't get me wrong I'm not a fan of the chatbots and other LLM's, but any advanced spellchecker is probably using some form of 'machine learning'

I get that you are feeling slint is not GPL, but I do not understand where that feeling comes from.

I think it's because the for-profit nature of the company may not create an actual community of FOSS enthusiasts around it. So if something were to happen to the business side of Slint-the-company, there would not be a strong community with known leaders and vision to save the situation. It's not like this is guaranteed for FOSS projects, but it's much more likely there. Single-person FOSS projects are scary to me for this reason as well.

That is the biggest factor for me. (There are other important factors, too.)

Did you look at Loco?

Interesting, do tell us how its going. Django's appeal to me is mostly with the ecosystem and readily available plugins and at the very least the admin. This just saves soo much time. Maybe rust based packages accelerating django is the way to go for me.

Saw Diesel mentioned, but also wanted to throw SeaORM out there. Might be worth looking into as well.

Did you give diesel orm a go? It is fairly mature at this point.

No, the attribute is unsafe. An unsafe function is marked unsafe fn.

Also, unsafe by itself just means there are invariants that must me manually upheld to avoid unsound behavior. If those invariants are upheld, then it doesn't matter if it's unsafe.

Wouldn't that make the body of the function unsafe too?

I would recommend reading up some materials on FFI in Rust

Yeah, I'm slowly getting to that

#[unsafe(export_name = "my_super_duper_function")]
pub fn foo() {}

I would recommend reading up some materials on FFI in Rust if you're interested. Calling functions in Rust from C and in C from Rust (or even languages other than C) is both extremely common and a primary usecase of the language.

Those are good to know, thanks. But as far as I understand, attribute enforces unsafe, repr is more about the data layout. Right?

But in there, I've found https://github.com/mozilla/cbindgen. Wicked

https://doc.rust-lang.org/reference/abi.html#the-no_mangle-attribute https://doc.rust-lang.org/nomicon/other-reprs.html#reprc

Does no_mangle and repr(c) do that?

It would be cool if there was an option to tell compiler how to name the object in the end. A strength of C mangling (or rather lack of it) is that you can take the object file and know beforehand the names. With mangling that will always depend on the version of the compiler. In practice, while mangled names are kind of stable, mangled C++ names are not really reliable in the real world

If we could tell the compiler "in the end name/alias this function as prefix_or_name_of_cargo_my_super_duper_function", we could then easily call it in an assembler/pure C/etc
It could even be a separate wrapper. only for exposing stable function names in the object files

The std::offload project is kinda cool. Hadn't heard about that before.

It'll be interesting to see where that leads.

I was curious to what cargo-script is. Here is more about that project: https://github.com/epage/cargo-script-mvs/blob/main/0000-cargo-script.md