Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3396912
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T04:27:54+00:00 2026-05-18T04:27:54+00:00

Having read the following at http://golang.org/doc/effective_go.html#arrays … Arrays are values. Assigning one array to

  • 0

Having read the following at http://golang.org/doc/effective_go.html#arrays…

  • Arrays are values. Assigning one array to another copies all the
    elements.
  • In particular, if you pass an array to a function, it will receive a copy
    of the array, not a pointer to it.

… I expect in the following code that arr2 to be distinct from arr, and main()‘s arr to be distinct from shuffle()‘s arr. Can someone please explain why the following code shuffles arr2? I know Go is still a young language; perhaps the treatment of arrays has changed?

package main

import (
        "fmt"
        "rand"
        "time"
)

func shuffle(arr []int) {
        rand.Seed(time.Nanoseconds())
        for i := len(arr) - 1; i > 0; i-- {
                j := rand.Intn(i)
                arr[i], arr[j] = arr[j], arr[i]
        }
}

func main() {
        arr := []int{1, 2, 3, 4, 5}
        arr2 := arr
        shuffle(arr)
        for _, i := range arr2 {
                fmt.Printf("%d ", i)
        }
}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T04:27:54+00:00Added an answer on May 18, 2026 at 4:27 am

    I think your problem is that you’re confusing arrays and slices.

    Arrays are fixed-length lists of values. You’re actually not using any arrays in your example. Arrays can be declared a few ways:

    arr1 := [3]int{1, 2, 3}   // an array of 3 integers, 1-3
    arr2 := [...]int{1, 2, 3} // same as the previous line, but we're letting
                              // the compiler figure out the size of the array
    var arr3 [3]int           // a zeroed out array of 3 integers
    

    You’re using slices. A slice is a reference to an underlying array. There are a few ways to allocate new slices:

    slice1 := []int{1, 2, 3}    // a slice of length 3 containing the integers 1-3
    slice2 := make([]int, 3)    // a slice of length 3 containing three zero-value integers
    slice3 := make([]int, 3, 5) // a slice of length 3, capacity 5 that's all zeroed out
    

    Any other slice assignments are just duplicating a reference to an array.

    Now that we’ve established that, the line

    arr := []int{1, 2, 3, 4, 5}
    

    creates a slice referencing an anonymous underlying array that contains the numbers 1-5.

    arr2 := arr
    

    duplicates that reference — it does not copy the underlying array. So there’s one underlying array and two references to it. That’s why the contents of arr2 change when you modify the contents of arr. They’re referencing the same array.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Having read the threads Is SqlCommand.Dispose enough? and Closing and Disposing a WCF Service
Having read up on quite a few articles on Artificial Life (A subject I
Having read an existing post on stackoverflow and done some reading around on the
Having read Fowler's Refactoring for a while, I still often catch myself thinking I
After having read that QuickSilver was no longer supported by BlackTree and has since
Having just read the first four chapters of Refactoring: Improving the Design of Existing
I'm having trouble reading a chunked response when using a StreamReader to read the
What are the benefits of having a member variable declared as read only? Is
Having a heckuva time with this one, though I feel I'm missing something obvious.
Having been a PHP developer on LAMP servers for quite a while, is there

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.