The behavior of `Computed` and `computed` is inconsistent

[CoderBuck]

Computed is lazy, but computed is not lazy, by design, it should be lazy ?

computed > _onComputedCreated

test code:

void main() {
  var x = signal(1);
  computed(() {
    print('computed 1');
    return x.value * 3;
  });
  Computed(() {
    print('computed 2');
    return x.value * 3;
  });
}

[rodydavis]

I need to hide the Computed class from the public API. It should only ever be called through the computed method

[rodydavis]

Fixed on 1.2.0

[CoderBuck]

computed( fn )

However, the behavior of the computed function varies in different compilation modes. Internally, the computed function calls _onComputedCreated, which in debug mode leads to the immediate execution of the fn within the computed function. However, in release mode, fn does not execute immediately, which could potentially cause issues in the production environment.

[rodydavis]

Oh that's right! For dev tools I added the value on create but can remove it now.

I can now grab the value on selection in dev tools

[rodydavis]

I will fix that on the next version and update devtools too

[rodydavis]

Fixed on 1.2.1