Non-Type Template Parameters  [[likely]] and [[unlikely]]  Calendars & Timezones  std::span  Feature Test Macros   Immediate Functions – consteval  constinit  Class Enums and using Lavavej Tuesday, September 15 • 13:3068 Feature Testing Macros  Allow you to detect if a compiler supports certain language and library features  Language feature test macros  __has_cpp_attribute(fallthrough) __cpp_char8_t  __cpp_coroutines  …  Standard Library feature test macros  __cpp_lib_concepts  __cpp_lib_ranges  __cpp_lib_scoped_lock  …69 Feature Testing Macros  Example: #if __has_include()

componentsTime aware layer • We will be using a feature layer that include hurricane data as features • Each feature has a specific start time and end time in the feature table • We will use these start and end features on the map • The JSON of the feature layer includes all the necessary information for the time slider - Start and end dates, time interval, etc. - Feature layer URLArcGIS Runtime for Qt - SDK

GH-261 by SuperWig27 GitHub Development Part 228 How We Use GitHub • Code: linear history, few feature branches • Issues: cxx20, LWG, bug, performance, etc. • Pull Requests: Used for all development and lit (LLVM Integrated Tester) • Linear history, squashed commits • Feature branches are uncommon • feature/spaceship, feature/format30 Issues • cxx20 issues track all remaining C++20 features •

Productivity At CppCon last year Announcing In Visual Studio 2019 version 16.11, C++20 is now feature complete • All features under /std:c++20 switch are production ready including modules, coroutines 27 – 12:30pm In-memory and Persistent Representations of C++ Gabriel Dos Reis – `Online _2 💡 Feature complete • C++23 • out_ptr and inout_ptr • contains for basic_string and basic_string_view • Other

PRs, discussions, etc. related to C++20 chrono: Extensions to (github.com) • Feature branch (feature/chrono) for rapid development and collaboration • Code Review Videos! • clocks, clock_cast

不透明的测试环境导致大量问题 4. 为每一次部署维护一个 Chart 版本 现状 效能提升场景： 2K+ 微服务、多语言、 Helm 、 K8s 多集群 1. 开发流程 提交代码到 Feature 分支 -> GitLab-CI 自动构建打包 Chart （写一堆复杂 的脚本 ） -> -> Rancher 上手动替换 Helm Chart 版本 -> 调试 Rancher 上手动替换 Helm Chart 版本 工具链： • GitLab （源码 + 服务 Chart 配 置） • Rancher 部署 分支策略： • feature -> develop/release -> master 环境策略： • 三套环境（ dev 、 qa 、 prod ） 现状：基于 GitLab + Helm Chart

Refactoring Find the correct mismatch delimiter pairs Aha Moment! It's sad, but we need to remove feature We care about performance and dev experience • A lot of fun! A lot of open-source experience •

datasets Scientific datasets Genomics Particle physics Astronomy & astrophysics Econometrics ML feature analytics and research Trading & financial data Fintech Insurance Investment banking Blockchain

(Javascript better than Dart) 利用 Rust 重塑移动应用开发 跨平台开发的优势和局 限性 Cons: - Performance - Native feature utilize - Existing Codebase 跨平台开发到到底 应该跨什么？ UI or Logic ? 利用 Rust 重塑移动应用开发 Rust 在移动端应 用的价值