todo.sr.ht

#701 Allocation type detection errors 2 years ago

Ticket created by ~gbear605 on ~sircmpwn/hare

I'm trying to allocate an array of integer slices. However, the types don't seem to be detected by alloc properly.

I try to immediately return the result of alloc:
fn create_array() *[64][]int = {
	return alloc([[]...]);
};
errors with
Error testalloc.ha:2:15: Return value **[64][]int is not assignable to function result type *[64][]int
If instead I just try to assign to a variable:
fn create_array2() void = {
	let arr: *[64][]int = alloc([[]...]);
};
The compiler errors with
Error testalloc.ha:2:12: Initializer is not assignable to binding type

#700 Assertion failed on array allocation pointer/value mismatch 2 years ago

Ticket created by ~gbear605 on ~sircmpwn/hare

See this simple example:
fn test() void = {
	let arr: [64][]int = alloc([[]...]);
};
I should presumably get an error saying that the types do not match - alloc returns a pointer while the variable is expecting a value. However, I instead see the compiler error
Assertion failed: htype->array.members == atype->array.members (src/check.c: check_expr_alloc_init: 320)
Error: harec: exited with signal 6
2022-05-14T18:53:45.987021200Z hare test: build failed

#687 Struct sub-typing tutorial infinite loop 2 years ago

Comment by ~gbear605 on ~sircmpwn/hare

Beyond that, the instantiation of the limitstream struct uses the ... syntax (on line 22), which seems to not be needed since all of the fields are set manually.

It also might be helpful to explain what that syntax does, since it's unclear to a learner whether it sets a default value (which would make sense) or if it copies the value last set like how the same syntax works for arrays.

#687 Struct sub-typing tutorial infinite loop 2 years ago

Ticket created by ~gbear605 on ~sircmpwn/hare

When running the Struct sub-typing tutorial, the program hangs. This reproduces by copying the code into a text file and calling hare run on it.

I am running Hare v20220328-2927-gf955d4e1ab-alpine.

Some debugging shows that the limit_write function is being called repeatedly.

#310 After failed secret adding, doesn't display existing secrets 4 years ago

Ticket created by ~gbear605 on ~sircmpwn/builds.sr.ht

On the secrets page, if you add a secret but mess up in some way (which you can simulate by going to the page and immediately submitting, without adding any information), then the page that it displays doesn't have your existing secrets visible, instead saying "You haven't added any secrets yet." Refreshing the page resolves the issue and makes the secrets appears again.

#265 Switch to CodeMirror for editing manifests 4 years ago

Comment by ~gbear605 on ~sircmpwn/builds.sr.ht

Can confirm that it works much better now. Thanks so much! :)

#265 Switch to CodeMirror for editing manifests 4 years ago

Ticket created by ~gbear605 on ~sircmpwn/builds.sr.ht

Ace, the current code editor, doesn't work well on iOS browsers since the hacks that it uses to display to the user don't act like the normal textfields. Based on discussion on IRC, we want to try using CodeMirror (https://codemirror.net), since it should be equal on desktop browsers and better on iOS.