romshark/Go-1-2-Proposal---Immutability issues and pull requests

#24 - Copying immutable scalar types to their mutable counterparts

Issue - State: open - Opened by romshark about 6 years ago - 4 comments
Labels: problem, help wanted

#23 - Mutability qualifier limited to package

Issue - State: open - Opened by networkimprov about 6 years ago - 16 comments
Labels: help wanted, discussion

#22 - Fix typos in README

Pull Request - State: closed - Opened by attilaolah about 6 years ago
Labels: mistake

#21 - Immutability and engineering

Issue - State: open - Opened by beoran about 6 years ago - 6 comments
Labels: discussion

#20 - Go 2: mutability qualification propagation

Issue - State: open - Opened by romshark about 6 years ago - 8 comments
Labels: problem, help wanted, discussion

#19 - Minor typo related to type aliasing?

Issue - State: closed - Opened by mewmew about 6 years ago
Labels: mistake

#18 - Strings are already immutable in Go

Issue - State: closed - Opened by mewmew about 6 years ago - 3 comments
Labels: question

#17 - Fix typo in ReadOnly interface example and remove unmatched right parenthesis

Pull Request - State: closed - Opened by mewmew about 6 years ago
Labels: mistake

#16 - Inconsistent position of 'const' between immutable targets of pointers and slices

Issue - State: open - Opened by dolmen about 6 years ago - 7 comments

#15 - typo: it's -> its

Issue - State: closed - Opened by bradfitz about 6 years ago

#14 - Redesign: Propose Implicit Casting of Mutable- to Immutable Types

Issue - State: closed - Opened by romshark about 6 years ago
Labels: problem

#13 - Describe the "immutability by default" language concept

Issue - State: closed - Opened by romshark about 6 years ago - 1 comment

#12 - Clarify the behavior of the address operator `&` on immutable types

Issue - State: closed - Opened by romshark about 6 years ago
Labels: enhancement

#11 - Investigate channel immutability

Issue - State: closed - Opened by romshark about 6 years ago - 1 comment
Labels: investigation

#10 - Add casting specification to required language changes

Issue - State: closed - Opened by romshark about 6 years ago

#9 - Make it clear whether const qualifier can't be "casted away"

Issue - State: closed - Opened by quasilyte about 6 years ago - 6 comments
Labels: problem

#8 - Describe const pointer to const data before it's used in a proposal text

Issue - State: closed - Opened by quasilyte about 6 years ago - 4 comments

#7 - Add FAQ question: why not use copy-receiver instead of const receiver

Issue - State: closed - Opened by romshark about 6 years ago - 1 comment
Labels: FAQ

#6 - Notes on the proposal

Issue - State: closed - Opened by roman-kulish about 6 years ago - 2 comments

#5 - Elaborate on addressability

Issue - State: closed - Opened by acln0 about 6 years ago - 1 comment
Labels: problem

#4 - Elaborate on const interfaces

Issue - State: closed - Opened by romshark about 6 years ago - 1 comment
Labels: problem, FAQ

#3 - Update README.md and some questions/comments

Pull Request - State: open - Opened by onokonem about 6 years ago
Labels: question

#2 - Elaborate on slice aliasing

Issue - State: closed - Opened by romshark about 6 years ago
Labels: FAQ

#1 - Add FAQ question about the qualifier keyword