You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since ChplFormat / chplSerializer exist to emit objects in a similar manner to Chapel source code, I would expect it to emit a domain in the same format as a domain literal.
For example:
use IO;
use ChplFormat;
var D = {1..10};
stdout.withSerializer(new chplSerializer()).writeln(D);
This emits
["1..10"]
But I would expect it to emit
{1..10}
Perhaps we could apply whatever exception we are using for the default serializer for ranges also to the chplSerializer here?
The text was updated successfully, but these errors were encountered:
This is an unintended side effect of #23392 , which changed some IO behavior to print out domains as lists and ranges as strings when the serializer is not the default serializer.
I'll take a look at updating the chplSerializer implementation to add an exception for ranges and domains.
I'm throwing the 'user issue' label on this since it sounds like @redhatturtle hit this on this Discourse thread (which may have led @mppf to post this?) and the 'bug' label since @benharsh indicated that it was an unintentional change in behavior.
Since
ChplFormat
/chplSerializer
exist to emit objects in a similar manner to Chapel source code, I would expect it to emit a domain in the same format as a domain literal.For example:
This emits
But I would expect it to emit
Perhaps we could apply whatever exception we are using for the default serializer for ranges also to the
chplSerializer
here?The text was updated successfully, but these errors were encountered: