Go vs. GoPlus(Go+) 许式伟 x@goplus.org 2021-6-27 北京 话外: 模板 Go 篇 谁是最成功的语言？ • 1970 – 至今 -什么语言是最成功的？ • C (1970) • C++ (1979) • Objective-C (1986) • Java (1994) • C# (2002) • Go (2009) 2012年8月 C 是 50

Top 5 improvements to Debugging Go Code in VS Code in the last year Ramya Rao Software Engineer, Microsoft Maintainer of the Go plugin to VS Code Add/remove breakpoints when in the middle of

使用VS Code进行Python开发 的最佳实践 杭州美登科技 杜逸先 目录 CONTENTS 什么是VS Code VS Code与Python 最佳实践 提问时间 什么是VS Code 什么是VS Code 什么是VS Code 什么是VS Code 1. 开源+跨平台 2. 轻量级+丰富的插件生态 3. 开箱即用+高度自定义（颜色主题、按键绑定、版本控制工具等） VS Code与Python VS Code与Python VS Code与Python——Autocomplete and IntelliSense VS Code与Python——Autocomplete and IntelliSense VS Code与Python——Refactoring(Extract Variable) VS Code与Python——Refactoring(Extract t Method) VS Code与Python——Refactoring(Sort imports) VS Code与Python——Linting VS Code与Python——Linting VS Code与Python——Formatting VS Code与Python——Formatting VS Code与Python——Debugging VS Code与Python——Debugging

Leading Chipmaker Details on Page 38 AI User + Usage + CapEx Growth = Unprecedented 2.2 Internet vs. Leading USA-Based LLM: Total Current Users Outside North America Note: LLM data is for monthly Monetization Threats = Rising Competition + Open-Source Momentum + China’s Rise 5 Leading USA LLMs vs. China LLM Desktop User Share Note: Data is non-deduped. Share is relative, measured across six leading Monetization Threats = Rising Competition + Open-Source Momentum + China’s Rise 5.1 China vs. USA vs. Rest of World Industrial Robots Installed Note: Data as of 2023. Source: International Federation

x86-64 gcc 14.2 -O2 -std=c++20 x86-64 (AMD64) Microsoft ABI x64 calling convention x64 msvc v19.40 VS17.10 -O2 /std:c++20 armv7-a System V ABI Procedure Call Standard for the Arm® Architecture armv7-a x86-64 gcc 14.2 -O2 -std=c++20 -m32 x86 (IA-32) Microsoft ABI calling conventions x86 msvc v19.40 VS17.10 -O2 /std:c++20 20Things are complicated 21 We’ll be looking for simple guidelines to navigate parameter 24 https://godbolt.org/z/ea9M3G94sarmv8-a clang 18.1.0 x86-64 gcc 14.2 x64 msvc v19.40 VS17.10 str xzr, [x8] ret mov QWORD PTR [rdi], 0 mov rax, rdi ret sub rsp, 24 xor eax, eax

Akinci C++ Cross-platform and CMake Product Manager for Visual Studio and VS Code Alexandra Kemper PM for the C++ Extension for VS CodeBefore we get started… Join #visual_studio channel on CppCon Discord soft C++ 1 Let's talk VS Code – Built on open source to run anywhere you are 2 Hello Again, World – Getting Started with C++ & CMake 3 Advanced Debugging & Testing - Using VS Code to build the Endless else is new in VS Code? – Dev Containers, Makefiles & More AgendaMicrosoft C++ Built on open source Runs anywhere you are Let’s Talk VS CodeMicrosoft C++ Why should I use VS Code? Light-weight

arch=x86 $ conan create . demo/testing -pr my_gcc49_debug_profile ... $ conan create ... 5.1.4 Settings vs. Options We have used settings such as os, arch and compiler. Note the above package recipe also contains runtime (MD/MDd). To keep the package configurable for supporting static(MT)/dynamic(MD) linking with the VS runtime library, you can do the following: • Keep the compiler.runtime setting, e.g. do not implement in_local_cache: if self.settings.compiler == "Visual Studio": # NOTE: Use the real layout used in your VS projects, this is just an␣ ˓→example self.cpp_info.libdirs = ["%s_%s" % (self.settings.build_type

arch=x86 $ conan create . demo/testing -pr my_gcc49_debug_profile ... $ conan create ... 5.1.4 Settings vs. Options We have used settings such as os, arch and compiler. Note the above package recipe also contains setting. settings = "os", "compiler", "arch" def configure(self): # it is also necessary to remove the VS runtime if self.settings.compiler == "Visual Studio": del self.settings.compiler.runtime def build(self): runtime (MD/MDd). To keep the package configurable for supporting static(MT)/dynamic(MD) linking with the VS runtime library, do the following: • Keep the compiler.runtime setting, i.e. do not implement the

arch=x86 $ conan create . demo/testing -pr my_gcc49_debug_profile ... $ conan create ... 6.1.4 Settings vs. options We have used settings as os, arch and compiler. But the above package recipe also contains setting. settings = "os", "compiler", "arch" def configure(self): # it is also necessary to remove the VS runtime if self.settings.compiler == "Visual Studio": del self.settings.compiler.runtime def build(self): If we want to keep the package configurable for supporting static(MT)/dynamic(MD) linking with the VS runtime library, some extra work is needed. Basically: • Keep, the compiler.runtime setting, i.e.

arch=x86 $ conan create . demo/testing -pr my_gcc49_debug_profile ... $ conan create ... 5.1.4 Settings vs. Options We have used settings such as os, arch and compiler. Note the above package recipe also contains setting. settings = "os", "compiler", "arch" def configure(self): # it is also necessary to remove the VS runtime if self.settings.compiler == "Visual Studio": del self.settings.compiler.runtime def build(self): runtime (MD/MDd). To keep the package configurable for supporting static(MT)/dynamic(MD) linking with the VS runtime library, do the following: • Keep the compiler.runtime setting, i.e. do not implement the