Kurtis Rader,
Stop it. When you are in a hole, stop digging.
When you don't understand a question or topic, don't launch ad hominem
attacks, calling people's questions silly. That's nasty and it's against
the Go Code of Conduct.
Like Jan, Rob, and Volker, I found it to be an interesting question, worthy
of an answer. I wrote a program and looked at the executable code. Are we
silly too?
Peter
On Thursday, March 10, 2022 at 12:29:54 AM UTC-5 Kurtis Rader wrote:
> On Wed, Mar 9, 2022 at 9:12 PM shan...@gmail.com <shan...@gmail.com>
> wrote:
>
>> Um
>>
>> Really?
>>
>> Which of these things are you specifically trying to prevent happening
>> - Curiousity
>> - Creativity
>> - Asking questions
>> - Some combination of the above
>>
>> I mean, I appreciate that you think that people should *know* whatever it
>> is you think you know, but that's a really *really* poor response
>>
>
> Yes, your question was silly. The limit is going to be both platform
> dependent and dependent on the resources (e.g., memory) available on the
> platform. Your question is silly because regardless of the fundamental
> limits imposed by the Go language or the platform it runs on absolutely no
> one will ever write a function that gets within many orders of magnitude of
> the limit. So your question is interesting in a hypothetical sense but not
> in a practical sense. For the former I suggest you start a research project
> and write a paper for review that explains why, or why not, the existing
> limit is a problem.
>
>
>> On Thursday, March 10, 2022 at 4:08:02 PM UTC+11 Kurtis Rader wrote:
>>
>>> On Wed, Mar 9, 2022 at 8:38 PM Jan Mercl <0xj...@gmail.com> wrote:
>>>
>>>> A linked list, for example, consists of pointers to pointers to
>>>> pointers...
>>>>
>>>> Why should any limit exist to the length of the list except resources
>>>> available?
>>>>
>>>
>>> Yes, but the O.P. was asking about a silly example. Specifically, when
>>> defining a function that receives pointers how many levels of indirection
>>> are allowed in the declaration. In practice 99.9% of the time a single
>>> level of indirection is specified and 0.09% of the time two levels are
>>> specified. Etcetera. For example, if
>>>
>>> func wtf(i ********int) {
>>> }
>>>
>>> is supported, which has eight levels of indirection, why isn't 16? 32?
>>> 64? Etcetera levels of indirection supported when defining a function. It's
>>> a silly question that shows the O.P. doesn't understand how compilers work.
>>> Let alone how people use languages like Go in real life.
>>>
>>>
>>>> On Thu, Mar 10, 2022, 03:59 shan...@gmail.com <shan...@gmail.com>
>>>> wrote:
>>>>
>>>>> This morning someone asked about dereferincing a pointer to a pointer
>>>>> to a pointer
>>>>>
>>>>> At first nobody had ever thought about, let alone knew the answer, but
>>>>> some example code was shown, and sure enough ***val is possible
>>>>> ```
>>>>> package main
>>>>>
>>>>> import "fmt"
>>>>>
>>>>> func main() {
>>>>> a := 0
>>>>> b := &a
>>>>> c := &b
>>>>> UltimatePointOne(&c)
>>>>> fmt.Println(a)
>>>>> }
>>>>>
>>>>> func UltimatePointOne(n ***int) {
>>>>> ***n = 1
>>>>> }
>>>>> ```
>>>>>
>>>>>
>>>>> On a lark a go playground example was tried to find what the maximum *
>>>>> is in Go
>>>>>
>>>>> https://go.dev/play/p/YhibY3p7TSD
>>>>>
>>>>> There's 28 there, but it's not the limit
>>>>>
>>>>> Does anyone know what the upper bound on this could be?
>>>>>
>>>>> 256 * ?
>>>>>
>>>>> 32k * ?
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "golang-nuts" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to golang-nuts...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/golang-nuts/60cf1568-31d3-426e-bfdc-0b4b98b53acdn%40googlegroups.com
>>>>>
>>>>> <https://groups.google.com/d/msgid/golang-nuts/60cf1568-31d3-426e-bfdc-0b4b98b53acdn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "golang-nuts" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to golang-nuts...@googlegroups.com.
>>>>
>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/golang-nuts/CAA40n-WZwmcC6aVyvO3H42c9WeuL%2BPEimApdOPgR20cS_nPU%2Bw%40mail.gmail.com
>>>>
>>>> <https://groups.google.com/d/msgid/golang-nuts/CAA40n-WZwmcC6aVyvO3H42c9WeuL%2BPEimApdOPgR20cS_nPU%2Bw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>
>>> --
>>> Kurtis Rader
>>> Caretaker of the exceptional canines Junior and Hank
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "golang-nuts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to golang-nuts...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/golang-nuts/974ff13d-59ff-41f5-90a2-9a3ccd08f10dn%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/golang-nuts/974ff13d-59ff-41f5-90a2-9a3ccd08f10dn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Kurtis Rader
> Caretaker of the exceptional canines Junior and Hank
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/80cccc38-6e7b-488e-90bb-4883e549375en%40googlegroups.com.
