search for: orderedness

The expressions > x<-factor(x) and > class(x)<-"factor" behave differently when x is already an ordered factor. It may not be a bug but it caught me out when I was trying to remove the "orderedness" from a factor variable. The following R code illustrates the difference. Is this difference between the 2 commands desirable? > x<-1:3 > class(x) NULL > x<-ordered(x) > class(x) [1] "ordered" "factor" > x<-factor(x) > class(x) [1] "ordered&...

...ction* specific info that it grabs from the instruction you pass to getLocation. IE it includes noalias data that it tries to match against other instructions. So we already have broken this abstraction to return better answers :) Is there a good reason it shouldn't also grab the volatileness/orderedness from the original instruction, store it and use it to try to give better getModRefInfo answers too? Nothing that involves walking, sure, but it can trivially give the same answer to this case, which is "the volatile load does not affect the regular load".

First, let me apologize in advance if this is the wrong place to submit a suggestion for a change to functions in the base-R package. It never really occurred to me that I'd have an idea worthy of such a change. My idea is to provide an upgrade to all the "sets" tools (intersect, union, setdiff, setequal) that allows the user to apply them in a strictly algebraic style. The