now/time/day gives different answer than now/time and then asking for /day

[Siskin-Bot]

Submitted by: Hostilefork

If you extract a TIME! from NOW, you can't pick a /DAY out of it:

>> t: now/time
== 22:00:59

>> t/day
** Script error: cannot access day in path t/day

But if you do the pathing all at once, it doesn't get an error...it just ignores that you asked for the /DAY

>> now/time/day
== 22:00:57

FWIW, Red 0.6 has a similar bug when the path is done all at once...but instead of giving back the time, it gives back the hour:

>> now/time/day
== 22

---

^{Imported from: metaeducation#2286}

Comments:

---

Hostilefork added Type.bug and Red.has.this.too on Jan 23, 2018

---

[Oldes]

>> now/time
== 17:22:23

>> now/time/precise
== 17:22:29.117

>> now/time/precise/day
** Script error: incompatible or invalid refinements
** Where: now
** Near: now/time/precise/day

>> now/time/day
** Script error: incompatible or invalid refinements
** Where: now
** Near: now/time/day

>> now/year/utc
** Script error: incompatible or invalid refinements
** Where: now
** Near: now/year/utc