Inline if with nil pointer

[onordgren]

Inline if with nil pointer

[markuswustenberg]

Hmm. Yeah, I get your point. I still think If has value, though, because it's so easy to inline components conditionally that would otherwise need to be branched elsewhere. Alternatively, one can use the IIFE pattern from Javascript-land (https://en.wikipedia.org/wiki/Immediately_invoked_function_expression).

[markuswustenberg]

@egeozcan @onordgren if you like and have the time, I'd be happy if you had a look at my proposed lazy evaluation solution at #156. I think I've finally arrived at an API I like.

[markuswustenberg]

Hi @onordgren , thank you for taking the time to file an issue! My answer time is a bit longer than usual, I've got the flu. 🤧

I agree that this is surprising behaviour, but actually a consequence of the design of gomponents itself. As you probably know, a component is basically (most often) a function. The functions are called inline in your example, and the component given to the g.If is always evaluated, but the result may be discarded. That's the reason for your nil pointer error.

I've explored possible solutions for this in #99 and #101, but haven't found a good one yet. Maybe I should use this opportunity to revisit the problem. Feedback and input appreciated. 😊

[markuswustenberg]

I tried an implementation for a solution, but I'm not entirely satisfied. If anyone wants to have a look and post their thoughts, they are very welcome!

[egeozcan]

Hi, a new user of the library here!

My humble suggestion is deprecating g.If and suggesting creating a function with an early nil return if the parameter does not satisfy. The language simply does not have the extensibility to enable any more elegant solution. But of course, I may be wrong and any pointers to alternative approaches would help a lot.

[markuswustenberg]

Hi @egeozcan , thanks for chiming in.

What you're proposing is essentially what the current implementation does:

func If(condition bool, n Node) Node {
	if condition {
		return n
	}
	return nil
}

The problem lies not in what the function does, but when parameters are evaluated when using it. Because gomponents is all just nested functions, the innermost function and its parameters is evaluated before we even reach the If, and that's where the nil panics occur. The only way around that is to guard against nil in a custom inline function (which returns a Node), or check for nils earlier in the component and behave appropriately.

Or am I misunderstanding your suggestion?

[egeozcan]

hi @markuswustenberg, well I meant not using a generic function, and using a custom function to do this. the g.node is super easy to compose so I humbly suggested that, that should be encouraged instead of offering abstractions that can't cover some cases such as the one discussed and may cause confusion. thanks for the detailed reply 😊