深入Go Module 鸟窝 细节、使用、坑以及未来 鸟窝 • Go微服务框架rpcx作者 • Go并发编程实战课专栏作者 • 《Scala集合技术手册》作者 目 录 Go 版本管理历史 01 认识 Go Module 02 使用 Go Module 03 血泪史 04 Go Module 未来特性 05 Go版本管理历史 第一部分 Go版本历史 GOPATH /2012/go mod /2018/ go1.11,go1.12~go1.17 Go module历代变更 Go1.12 • GO111MODULE • 正式推出 • 影响go命令 Go1.13 • GO111MODULE未 如预期去掉 • GOPROXY • 影响go命令 Go 1.14 • go命令全面支持 module,可以产 品使用 • 支持- mod=vendor • GOINSECURE GO111MODULE默 认为on • 又是一堆go命令 不兼容 • retract • -e • 禁止特殊import path Go 1.17 • Lazy module loading • // Deprecated: comment • 不包含go directive，默认 为go 1.11 • 又是一堆go命令 不兼容 认识 Go Module 第二部分

nn.Module 主讲人：龙良曲 Magic ▪ Every Layer is nn.Module ▪ nn.Linear ▪ nn.BatchNorm2d ▪ nn.Conv2d ▪ nn.Module nested in nn.Module 1. embed current layers ▪ Linear ▪ ReLU ▪ Sigmoid ▪ Conv2d ▪ ConvTransposed2d

can be used in some cases. The most significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: dynamically load the standard modules using the LoadModule directive, then you will need to account for the module name changes mentioned above. If you choose to use the new default configuration file for version this directive in your config file, you can add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name

can be used in some cases. The most significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: dynamically load the standard modules using the LoadModule directive, then you will need to account for the module name changes mentioned above. If you choose to use the new default configuration file for version this directive in your config file, you can add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name

can be used in some cases. The most significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: dynamically load the standard modules using the LoadModule directive, then you will need to account for the module name changes mentioned above. If you choose to use the new default configuration file for version this directive in your config file, you can add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name

can be used in some cases. The most significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: dynamically load the standard modules using the LoadModule directive, then you will need to account for the module name changes mentioned above. If you choose to use the new default configuration file for version this directive in your config file, you can add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name

can be used in some cases. The most significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: dynamically load the standard modules using the LoadModule directive, then you will need to account for the module name changes mentioned above. If you choose to use the new default configuration file for version this directive in your config file, you can add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name

more information in either the New Features document, or in the src/CHANGES file. Application and module developers can find a summary of API changes in the API updates overview. This document describes are commented out in the configuration file. configure: the "most" module set gets built by default configure: the "reallyall" module set adds developer modules to the "all" set Run Time Configuration using the new module mod_authz_host. The old access control idioms should be replaced by the new authentication mechanisms, although for compatibility with old configurations, the new module mod_access_compat

more information in either the New Features document, or in the src/CHANGES file. Application and module developers can find a summary of API changes in the API updates overview. This document describes are commented out in the configuration file. configure: the "most" module set gets built by default configure: the "reallyall" module set adds developer modules to the "all" set Run Time Configuration using the new module mod_authz_host. The old access control idioms should be replaced by the new authentication mechanisms, although for compatibility with old configurations, the new module mod_access_compat