slice

I was following the example https://tour.golang.org/moretypes/10 I modified the code expecting to get the same result. I did not. Is this a bug, or a documentation error? The tour states A nil slice has a length and capacity of 0. My y variable has a length and capacity of 0. package main import "fmt" func myPrint(z []int) { fmt.Println(z, len(z), cap(z)) if z == nil { fmt.Println("nil!") } } func main() { var z []int y := []int {} myPrint(z) myPrint(y) } Here is my output. [] 0 0 nil! [] 0 0 I was expecting a second "nil"~ Why didn't I get it? The doc you referenced states that a nil slice

In Python (2 and 3). Whenever we use list slicing it returns a new object, e.g.: l1 = [1,2,3,4] print(id(l1)) l2 = l1[:] print(id(l2)) Output >>> 140344378384464 >>> 140344378387272 If the same thing is repeated with tuple, the same object is returned, e.g.: t1 = (1,2,3,4) t2 = t1[:] print(id(t1)) print(id(t2)) Output >>> 140344379214896 >>> 140344379214896 It would be great if someone can shed some light on why this is happening, throughout my Python experience I was under the impression empty slice returns a new object. My understanding is that it's returning the same object as tuples are

I have a byte array, with a fixed length of 4. token := make([]byte, 4) I need to set each byte to a random byte. How can I do so, in the most efficient matter? The math/rand methods do not provide a Random Byte function, as far as I am concerned. Perhaps there is a built-in way, or should I go with generating a random string and converting it to a byte array? Package rand import "math/rand" func Read func Read(p []byte) (n int, err error) Read generates len(p) random bytes from the default Source and writes them into p. It always returns len(p) and a nil error. f unc (*Rand) Read func (r

Looking at this tutorial I saw the following code suggestion in one comment: init:function(callback){ var that =this ; return $http.jsonp(this.url).success( function(data){ that.availableGenres = that.getGenres(data); that.results = that.getResults(data); if(callback)callback.apply(null,[].slice.call(arguments)) } ) } But this line callback.apply(null,[].slice.call(arguments)) looks weird to me. Why not just: callback.apply(null, arguments) ? Because I don't like when I don't understand the point of something I played around with this Fiddle to understand the need of slice function in there.

Due to showing MPR view based on Dicoms. I've made a 3D array from series of dicom files. And I show it from Coronal and Sagittal sides. My 3D array includes: - z = count of dicoms - c = column value for every dicoms - r = Row value for every dicoms But I have a problem. When there is some space between slices, image is made by this way doesn't show a correct view. Because I can not think of simulation distance between them! I don't know how to calculate space between slices? I want to add extra space between slices. for example, If space between slices is 4. I have to add 4 time z inner

With single indexed dataframe I can do the following: df2 = DataFrame(data={'data': [1,2,3]}, index=Index([dt(2016,1,1), dt(2016,1,2), dt(2016,2,1)])) >>> df2['2016-01 : '2016-01'] data 2016-01-01 1 2016-01-02 2 >>> df2['2016-01-01' : '2016-01-01'] data 2016-01-01 1 Date time slicing works when you give it a complete day (i.e. 2016-01-01), and it also works when you give it a partial date, like just the year and month (2016-01). All this works great, but when you introduce a multiindex, it only works for complete dates. The partial date slicing doesn't seem to work anymore df = DataFrame(data=