From @masak

<TimToady> note that nom is not behaving according to spec wrt S02​:3365
<TimToady> :8(42) is supposed to fail

Use of the functional form on anything that is not a string will throw
an exception explaining that the user has confused a number with the
textual representation of a number. This is to catch errors such as
a C<​:8(777)> that should have been C<< :8<777> >>, or the attempt to use
the function in reverse to produce a textual representation from a number.

< masak> TimToady​: hm, I wonder if we have an RT ticket for that...
* masak looks
<masak> seems we don't.
<moritz> TimToady​: :8(Numeric) in general?
<TimToady> :8(none(Str)) :)
< masak> nom​: say :8(42)
<p6eval> nom 327fc9​: OUTPUT«34␤»
* masak submits rakudobug
<TimToady> note also that :8<42> is a special form, so is not subject
to val() semantics
<moritz> and subject to Str.Numeric semantics?
<TimToady> though even if it were, <42> counts 42 as a Str in addition to an Int

From @jnthn

On Sun Jan 08 12​:30​:27 2012, masak wrote​:

<TimToady> note that nom is not behaving according to spec wrt
S02​:3365
<TimToady> :8(42) is supposed to fail

Use of the functional form on anything that is not a string will throw
an exception explaining that the user has confused a number with the
textual representation of a number. This is to catch errors such as
a C<​:8(777)> that should have been C<< :8<777> >>, or the attempt to
use
the function in reverse to produce a textual representation from a
number.

< masak> TimToady​: hm, I wonder if we have an RT ticket for that...
* masak looks
<masak> seems we don't.
<moritz> TimToady​: :8(Numeric) in general?
<TimToady> :8(none(Str)) :)
< masak> nom​: say :8(42)
<p6eval> nom 327fc9​: OUTPUT«34␤»
* masak submits rakudobug
<TimToady> note also that :8<42> is a special form, so is not subject
to val() semantics
<moritz> and subject to Str.Numeric semantics?
<TimToady> though even if it were, <42> counts 42 as a Str in addition
to an Int

Now it constrains to Str. So​:

:8(42)
Nominal type check failed for parameter '$str'; expected Str but got Int
instead

Tagging testneeded.

/jnthn

The RT System itself - Status changed from 'new' to 'open'

From @moritz

Now tested in S02-literals/radix.t.

@moritz - Status changed from 'open' to 'resolved'