u/ntrel2

A fragment isn't always clear enough. E.g. iface is better than inter or face. In Zig, I find comptime too long and there is no good fragment for that - ct would work IMO. Personally I find func a bit long, especially for people used to C where there's no keyword. When Rust came out, I once argued that fn was too short - now I love it.

I suppose it's something that the link says 'Not Suitable for Vegans', I wonder if that is on the box though - it would be helpful if manufacturers did that.

These were both great but sadly no longer available in the big sainsbury's I use

I've seen discussions on dlang forums where even seasoned D developers (meaning developers of D itself, not just developers of applications in D) got totally confused and didn't realise that the routine they were talking about was supposed to run at compile time, not runtime.

I don't recognize that at all. The D spec clearly defines the contexts where CTFE will be done, and they are always easy to recognize due to the syntax for anyone familiar with D: https://dlang.org/spec/function.html#interpretation

Stop trading with Israel completely until Israelis move back to the pre-1967 borders. It's very hard to enforce sanctions on only the illegal settlements.

Ran, not run. No longer the people who actively antagonised the left under starmer

I'll give you BYC and planet smasher, but solar winds has quite a lot of dialogue, and N9 doesn't really have much vocals so it's not much of a 'song'. But if we're counting non-traditional song structure then there's plenty more on dark matters I could add to the list. I suppose it is subjective as you say.

It sounds like those developers should be using many pointers instead then.

Subtraction is different because it produces an integer, so it can be allowed on single element pointers. Addition should not be allowed on single element pointers IMO because that produces a different pointer.

OK, but no compile-time detection of a pointer to stack data escaping its scope? I know you said there's no borrow checker (which is more complex).

But that breaks the type system, I really don't think *void -> *T for any T should be implicit. C++ does not allow it.

Have you seen ziltoid live at the Albert hall? That really got me into dark matters

I'd say Death Ray, march of the poozers, ziltoid goes home and dimension Z are all standalone songs. The first album had 4 too IMO: ziltoidia attaxx, hyperdrive, colour your world and the greys as standalone songs. I know he plays by your command live, but I wouldn't really call that a standalone song.

In June he said ziltoid was 'up to bat next' after Ruby Quaker and that ziltoid had 'kind of lost his marbles a little bit' after being abandoned on the moon at the end of Z2. https://youtube.com/shorts/Dy1lLaZhL_w?is=ET-0Z7cStplXgTUI

I think the distinction between many pointer and normal pointer is interesting, but why allow pointer arithmetic (ptr + 1) for normal pointers? Surely a many pointer should be used instead?

Is there any compiler checking for stack pointer escaping? E.g.

let numbers = [1, 2, 3, 4, 5]; // stack allocated fixed size array?
let slice = numbers[1..4];
return slice;

Why does `*void` implicitly convert to `*i32` in `alloc_me` below?

extern fn malloc(usize) *void;

fn alloc_me[T](count: usize) *T {
malloc(@sizeof(T) * count) // here
}

fn main() {

let pointer = alloc_me #[i32](3);

I don't know what their plans are, but a compiler could track both mutable aliasing and uniqueness. Just that uniqueness wouldn't be a requirement for mutability.

No a scientific panel appointed by the government over 2 decades ago did

oh that must have been what i bought once, thought it was amazing, then never saw it again. No tuno is not like that, it's not like tuna really but it is cheap and ok but a bit chewy.

Gassing with CO2 is worse than bleeding to death.

So sorry, that would have made me feel despair. You give them a bad review?

'Flavourings' might not be vegan?

Nice tip about frozen mushrooms. Maybe they'd be good in risotto too. The old CG soup had rice blended into it for consistency and colour.

You can get the endianness using a field name instead of an arbitrary index. Whereas for the bytes, using the index is natural.

I'll check these out - I love Absolute Elsewhere!