How to break out from a unreturned await?

PeterPM

extends Node


signal value_changed(new_value)
var memo:
	set(value):
		memo = value
		value_changed.emit(value)
	get:
		return memo

func _ready() -> void:
	print(await handler())

var counter = 0
func handler():
	f1(4)
	f2(5)
	var toreturn = await value_changed
	memo = null
	counter +=1
	return toreturn

func f1(n):
	await get_tree().create_timer(n).timeout 
	memo = "lefunc"
	
func f2(n):
	var icounter = counter
	await get_tree().create_timer(n).timeout 
	if counter == icounter:
		memo = "timeout"

the above code works, if f1 is greater then f2 it timeouts, if its smaller, it returns the lefunc.

I guess this can fix.

Thanks @DaveTheCoder

xyz

PeterPM Why do all this when you can simply let awaitable() emit a signal that is connected to a function that executes print(2)?

PeterPM

It worked on field!

But now i am getting this pair of error over and over.
But all works

E 0:00:01:0623 script.gd:300 @ @memo_setter(): Resumed function 'inter()' after await, but script is gone. At script: res://SCRIPTS/script.gd:271
<Erro C++> Method/function failed. Returning: Variant()
<Origem C++> modules/gdscript/gdscript_function.cpp:197 @ resume()
<Rastreamento de Pilha>script.gd:300 @ @memo_setter()
script.gd:273 @ inter()
script.gd:300 @ @memo_setter()
script.gd:291 @ interfacer()
script.gd:-1599536512 @ interface()

E 0:00:01:0623 script.gd:300 @ @memo_setter(): Attempt to disconnect a nonexistent connection from 'Node:<Node#25753027822>'. Signal: 'value_changed', callable: 'GDScriptFunctionState::_signal_callback'.
<Erro C++> Condition "!s->slot_map.has(*p_callable.get_base_comparator())" is true. Returning: false
<Origem C++> core/object/object.cpp:1420 @ _disconnect()
<Rastreamento de Pilha>script.gd:300 @ @memo_setter()
script.gd:291 @ interfacer()
script.gd:-1599536512 @ interface()

PeterPM

xyz

Will not awnser, as the aprouch worked to reflect the exact behaviour i needed.

Messy is not to be refactored.

But yes, i pondered about this, but this level of indirection is working for the project.

Can you adress about the engine error i am now getting?

xyz

PeterPM Can you adress about the engine error i am now getting?

No, but I'll just put this here: don't mess with await if you don't fully understand it or can't control/debug it. Everything you do via awaiting on custom signals can be done without those awaits. It also typically ends up simpler that way.

DaveTheCoder

xyz don't mess with await if you don't fully understand it or can't control/debug it

But if you don't mess with things, you'll never understand them.

xyz

DaveTheCoder But if you don't mess with things, you'll never understand them.

Depends how your personality type deals with "messing". Hacker types learn from messing, for the most part. Non-hacker types just end up more confused. Statistically, non-hacker types are far more common in general population.

DaveTheCoder

xyz eneral population

This isn't the general population.

xyz

DaveTheCoder This isn't the general population.

I suppose so. Hard to tell with certainty though. Also, while messing is good for collecting bits of applied knowledge, it's weak for groking conceptual frameworks. The latter is what most people actually lack.

PeterPM

And for 24 + days i messed up on that.
and AWAITS are indeed a breed of the devil.

So after all that, i could'nt find a way to tacckle it elegantly...
SO!!! I just realized:
WhatchDog now has a Bonk on his hand.
Its the bonk of reincarnation.

TLDR:
If detected a far to long wait i just free the node and re-instanciate it with the previous state before freeze call.

Erich_L

Let me do my own TLDR:
you don't need await. If you think you need await, paste your code into chatgtp with your coding objectives and ask it to give a non-await solution

xyz

Erich_L You're joking, right?