Displaying 5 results from an estimated 5 matches for "setcontain".
Did you mean:
setcontains
2015 Jan 06
4
setequal: better readability, reduced memory footprint, and minor speedup
Hi,
Current implementation:
setequal <- function (x, y)
{
x <- as.vector(x)
y <- as.vector(y)
all(c(match(x, y, 0L) > 0L, match(y, x, 0L) > 0L))
}
First what about replacing 'match(x, y, 0L) > 0L' and 'match(y, x, 0L) > 0L'
with 'x %in% y' and 'y %in% x', respectively. They're strictly
equivalent but the latter
2015 Jan 08
3
setequal: better readability, reduced memory footprint, and minor speedup
...nted
> using match, so if we did as you suggest, I give it about three days before
> someone suggests to inline the function call... Readability of source code
> is not usually our prime concern.
>
> The && idea does have some merit, though.
>
> Apropos, why is there no setcontains()?
>
> -pd
>
> > On 06 Jan 2015, at 22:02 , Herv? Pag?s <hpages at fredhutch.org> wrote:
> >
> > Hi,
> >
> > Current implementation:
> >
> > setequal <- function (x, y)
> > {
> > x <- as.vector(x)
> > y <- as.vec...
2015 Jan 08
0
setequal: better readability, reduced memory footprint, and minor speedup
...u'll find that it is implemented using match, so if we did as you suggest, I give it about three days before someone suggests to inline the function call... Readability of source code is not usually our prime concern.
The && idea does have some merit, though.
Apropos, why is there no setcontains()?
-pd
> On 06 Jan 2015, at 22:02 , Herv? Pag?s <hpages at fredhutch.org> wrote:
>
> Hi,
>
> Current implementation:
>
> setequal <- function (x, y)
> {
> x <- as.vector(x)
> y <- as.vector(y)
> all(c(match(x, y, 0L) > 0L, match(y, x, 0L)...
2015 Jan 08
0
setequal: better readability, reduced memory footprint, and minor speedup
...o if we did as you suggest, I give it about three days before
>> someone suggests to inline the function call... Readability of source code
>> is not usually our prime concern.
>>
>> The && idea does have some merit, though.
>>
>> Apropos, why is there no setcontains()?
>>
>> -pd
>>
>> > On 06 Jan 2015, at 22:02 , Herv? Pag?s <hpages at fredhutch.org> wrote:
>> >
>> > Hi,
>> >
>> > Current implementation:
>> >
>> > setequal <- function (x, y)
>> > {
>> >...
2010 Aug 20
0
Wine release 1.3.1
...ed3d: Correctly calculate the resource size for ATI2N surfaces.
wined3d: Rename surface_calculate_size() to wined3d_format_calculate_size().
wined3d: Round up to complete compressed blocks in IWineD3DDeviceImpl_UpdateSurface().
wined3d: Fix a couple of typos.
wined3d: Remove SetContainer() from the public IWineD3DVolume interface.
wined3d: Remove SetContainer() from the public IWineD3DSurface interface.
wined3d: A volume's container is always a volume texture.
wined3d: Also store the subresource container type.
wined3d: Get rid of the now redundant SFL...