Viewing profile — pizlonator

From the second paragraph of fil-c.org: "Fil-C has no unsafe statement and only limited FFI to unsafe code." `zunsafe_call` is a weird thing to get hung up on as an "escape hatch",…

Genius.

How do you enforce this?

I have worked on both a major JS runtime and a .NET runtime. I have fixed hundreds of security bugs in JSC. Based on that, I have no doubt that what Fil-C does is safer. Just the a…

Saying something that you don’t believe isn’t trolling.

This thread is evidence of it. The OP is about Zig and now there are 40+ mentions of Fil-C initiated mostly by Rust folks and those comments are largely criticizing me personally. …

[flagged]

I never claimed that Fil-C is objectively better than Rust. As a long time PL researcher, I can, should, and will point out interesting corner cases of languages. Including in Fil-…

[flagged]

Steve, be reasonable. I never said Fil-C is “so much better” (let alone with all caps) than anything. I never called Rust “trash”. I think you’re taking this all too personally

This is a simple fact. The Fil-C runtime is tiny compared to TS and C#

First of all, it’s incredible that on a HN thread about a language that isn’t C, there are 46 mentions of Fil-C! You guys are obsessed! I make bold claims because they hold water. …

Yes, being able to build small and fast binaries in TS would be a valuable capability, which is why basically all of us who work in this space have thought of this idea and rejecte…

They will have untyped dependencies. That’s how the TS/JS ecosystem works. Note that “untyped dependency” means any code that says `any`.

Yeah - using quickjs at all in a thing that needs perf. Quickjs is hilariously slow. Midwits use it because it has “quick” in the name. - using floats for numbers and deferring int…

That explains why: - the architecture is idiotic. - they have zero credible perf numbers. I plan to benchmark it using generally accepted methods. Porffor makes careful trade offs …

Before I started talking about Fil-C, discussions about Rust’s memory safety lacked nuance: folks claimed that if you just compiled your code in Rust then it would be memory safe. …

Memory safety can be defined in more than one way, so it’s super worthwhile to figure out how to define it and what meets the definition and what doesn’t. We should do more of that…

other implementations of fat pointers (that I’m aware of) have no distinction between flight and rest; they store what I call flight pointers in memory literally. The closest techn…

The problem with this post is the extent to which it shows that its author has an unhealthy obsession with me personally. It’s weird but also oddly flattering. I don’t dislike Rust…

Yes

Invisicaps are not exactly fat pointers. Fat pointers show up inline in memory, which has a bunch of problems: - sizeof(void*) changes - either you let the bounds get corrupted by …

What a weird take. I think the limits of Rust’s memory safety are interesting to discuss, as are the limits of Fil-C’s perf and practicality. It’s best to discuss these things rati…

The “bug” in your example hinges on this: > if (p == bar) It is not in scope of memory safety to make sure that logic not related to memory accesses works as you expected. In Fil-C…

I define memory safety in terms of capabilities, which is a mainstream definition. The worst that can happen in a race is that you read or write an object that would have been acce…