vscode-cmake-tools VS swift

After that I would recommend installing the MS CMake Tools extensions (https://github.com/microsoft/vscode-cmake-tools/blob/main/do...), this discovers CMakeLists.txt files in the projects and then uses those to setup build- and debugging targets, and in general gives your an IDE-like experience, while still being more transparent than a "fat IDE" like Visual Studio or Xcode.

what do you mean? you need to create a CMakeLists.txt file, the extension can create one for you iirc, take a look at: https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/README.md

#https://medium.com/@onur.dundar1/cmake-tutorial-585dd180109b #https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/README.md cmake_minimum_required(VERSION 3.0.0) project(Zoom VERSION 0.1.0) include(CTest) enable_testing() set(CMAKE_CXX_STANDARD 17) if(${CMAKE_BUILD_TYPE} MATCHES Debug) message("Debug Build") add_definitions(-DDEBUG="Debug Build") elseif(${CMAKE_BUILD_TYPE} MATCHES Release) message("Release Build") add_definitions(-DRELEASE="Release Build") endif() #benXml add_library(benXml STATIC ${CMAKE_SOURCE_DIR}/lib/benXml/src/XmlRessource.cpp) target_sources(benXml PUBLIC ${CMAKE_SOURCE_DIR}/lib/benXml/src/include/tinyxml2.cpp) #benLog FILE(GLOB_RECURSE benLog_all_sources "lib/benLog/*.cpp") add_library(benLog STATIC ${CMAKE_SOURCE_DIR}/lib/benLog/src/Log.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogConfig.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogConsoleTarget.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogFileTarget.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/Logger.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogLevel.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogTarget.cpp ) target_link_libraries(benLog benXml) #Zoom FILE(GLOB_RECURSE all_sources "src/*.cpp") add_executable(Zoom ${CMAKE_SOURCE_DIR}/src/Zoom.cpp) target_sources(Zoom PUBLIC ${all_sources}) target_include_directories(Zoom PUBLIC src lib) target_include_directories(Zoom PUBLIC src) target_link_libraries(Zoom mingw32) target_link_libraries(Zoom SDL2main) target_link_libraries(Zoom SDL2) target_link_libraries(Zoom SDL2_mixer) target_link_libraries(Zoom SDL2_image) target_link_libraries(Zoom SDL2_ttf) target_link_libraries(Zoom box2d) target_link_libraries(Zoom benXml) target_link_libraries(Zoom benLog) set(CPACK_PROJECT_NAME ${PROJECT_NAME}) set(CPACK_PROJECT_VERSION ${PROJECT_VERSION}) include(CPack)

source

It sounds like you don't have a version of make itself installed in your environment. If you're using msys2 as your environment, you might have hit this bug, which at least has a workaround (symbolic link from mingw32-make.exe to make.exe )

Hey, what issues are you seeing with the CMake Tools extension? My team would definitely like to make sure that these issues are tracked here Issues · microsoft/vscode-cmake-tools (github.com). We'll get to them as soon as we can to make sure folks have a great experience with Code regardless of the build system they're on.

This algorithm produces biased result with probability 1/2^(32-bitwidth(N)). Using 64 or 128 random bits can make the bias practically undetectable. Comprehensive overview of the approach can be found here: https://github.com/apple/swift/pull/39143

Because of C/C++ interop, and integration with CMake, you can just add Swift to a Zephyr project and it pretty much Just Works. [The docs](https://github.com/apple/swift/blob/main/docs/EmbeddedSwift/...) should mostly apply to the Zephyr SDK as well.

Fortunately, the Observation framework is part of the Swift 5.9 standard library. We can learn more information by examining its source code.

They do! See https://github.com/apple/swift/blob/main/docs/LibraryEvoluti...

You can also see an example of what a different high level language integration with Swift ABI looks like here: https://github.com/dotnet/designs/blob/main/proposed/swift-i...

So is differentiable Swift a package for Swift or is it part of the Swift standard library? The video says go to swift.org but I can't find any info about differentiable Swift on that site.

Swift's Differentiable Programming Manifesto. Swift has a powerful differentiable programming component, integrated with the compiler.

You can do the same thing the other way around - https://github.com/apple/swift/blob/main/docs/Android.md.

Codable (along with other derived conformances like Equatable, Hashable, and RawRepresentable) is indeed built in to the compiler[0], but unlike Serde, it operates during type-checking on a fully-constructed AST (with access to type information), manipulating the AST to insert code. Because it operates at a later stage of compilation and at a much higher level (with access to type information), the work necessary is significantly less.

With ongoing work for Swift macros, it may eventually be possible to rip this code out of the compiler and rewrite it as a macro, though it would need to be a semantic macro[1] rather a syntactic one, which isn't currently possible in Swift[2].

[0] https://github.com/apple/swift/blob/main/lib/Sema/DerivedCon...

`Int` is a regular struct with a single stored property of type `Builtin.Word` . But the latter is a magical compiler built-in. Source for integer types is generated from this template - https://github.com/apple/swift/blob/9da65ca0a15fdf341649c994b0a77ec3b71f2687/stdlib/public/core/IntegerTypes.swift.gyb