You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've learned a lot from the go2go implementation as far as type checking, but we need to understand better how a compiled implementation of type parameters would be done.
We're not ready to do that in the main tree—among other things, there isn't even a final proposal yet—but it would be good to have somewhere public for the people doing the initial exploratory implementation to work.
This issue is to create a dev.typeparams branch in the Gerrit go repo, analogous to the other currently active branches:
dev.fuzz (exploratory fuzzing work),
dev.go2go (go2go translator work),
dev.link (linker work from last few cycles).
dev.types (exploratory new go/types package work),
The creation of this branch does not mean that the generics design draft is any farther along as far as being a proposal or accepted proposal. It just means we need a place to do the next round of implementation to learn more about it.
The text was updated successfully, but these errors were encountered:
We've learned a lot from the go2go implementation as far as type checking, but we need to understand better how a compiled implementation of type parameters would be done.
We're not ready to do that in the main tree—among other things, there isn't even a final proposal yet—but it would be good to have somewhere public for the people doing the initial exploratory implementation to work.
This issue is to create a dev.typeparams branch in the Gerrit go repo, analogous to the other currently active branches:
The creation of this branch does not mean that the generics design draft is any farther along as far as being a proposal or accepted proposal. It just means we need a place to do the next round of implementation to learn more about it.
The text was updated successfully, but these errors were encountered: