slice: fill builtin

[bangbangsheshotmedown]

Odin has copy builtin, but no equivalent for fill, instead it sits in a package you have to import yourself, this is inconsistent, and makes using slices annoying to use, it breaks the flow

I propose making the flll proc, a builtin

Odin/core/slice/slice.odin

Lines 407 to 415 in 8dc374a

	fill :: proc(array: $T/[]$E, value: E) #no_bounds_check {
	if len(array) <= 0 {
	return
	}
	array[0] = value
	for i := 1; i < len(array); i *= 2 {
	copy(array[i:], array[:i])
	}
	}

This is a builtin operation in languages that have slices as a core concept

builtin

// d

int[10];
slice[] = 42;

// zig

var slice: [10]u8 = undefined;
@memset(&slice, 42, slice.len);

// c3

int[10] slice;
slice[] = 42;

// rust

let mut slice = [0; 10];
slice.fill(42); 

// v

mut slice := []int{len: 10}
slice.fill(42)

// nim

var slice = newSeq[int]
slice.fill(42)

import

// c

#include <string.h>

int slice[10];
memset(slice, 0, sizeof(slice));

// odin

import "core:mem";

slice : [10]int
mem.fill(slice, 42);

dumb

// go

slice := make([]int, 10)
for i := range slice {
    slice[i] = 42
}

[Kelimion]

No thank you. We have slice.fill and slice.zero in core:slice.

[bangbangsheshotmedown]

that was not the point of the post, it was to discuss about having it as a built in, you didn't even give a chance for that discussion to happen

if you don't mind, can you answer the following questions?

• why is copy a built in, but not fill?
• what's the rational behind putting fill, a common builtin operation in most languages behind a package?

[gingerBill]

fill is not a common enough operation to warrant it being in builtin.

copy is used a hell of a lot in comparison/