🐛 Stream representation Is non-deterministic

[ccamel]

Issue

The current implementation of the Stream.WriteTerm function for streams outputs a pointer as part of the stream’s representation, which results in non-deterministic behavior.

prolog/engine/stream.go

Lines 82 to 86 in ea00e9b

	// WriteTerm outputs the Stream to an io.Writer.
	func (s *Stream) WriteTerm(w io.Writer, _ *WriteOptions, _ *Env) error {
	_, err := fmt.Fprintf(w, "<stream>(%p)", s)
	return err
	}

Analysis

Using the pointer (%p) to represent the stream makes the output non-deterministic, as pointer values change between executions. This is particularly problematic in our case, where we use the Prolog engine in our blockchain. Determinism is critical for ensuring consistent state, reproducibility, and validation across distributed nodes.

test :- 
  current_output(Out), 
  write_term(Out, []).

?- test.
<stream>(0x1400015b380)