FAQ

Search Discussions

  • Daniel Morsing at Nov 25, 2012 at 8:56 am
    This looks more like an invalid typecast than an invalid indirect to me.

    I don't think this is the right way to fix the reported bug.

    https://codereview.appspot.com/6850097/
  • Minux at Nov 25, 2012 at 9:08 am

    On Sunday, November 25, 2012, wrote:

    This looks more like an invalid typecast than an invalid indirect to me.
    no, a typecast should write (*a)(av).
    http://tip.golang.org/ref/spec#Conversions
  • Daniel Morsing at Nov 25, 2012 at 10:04 am
    Nevermind, I was mistaken.

    I still have this nagging feeling that this error will happen in some
    other context where top & (Erv | Etop) won't catch it.

    Off the top of my head, (top & (Erv | Etype)) != Etype, might do the
    job, but I'm not entirely sure.

    https://codereview.appspot.com/6850097/

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-dev @
categoriesgo
postedNov 25, '12 at 8:16a
activeNov 25, '12 at 10:04a
posts4
users3
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase