Lightning Talk: Initialisation in Modern C++ - Timur Doumler - CppNow 2022

Sdílet
Vložit
  • čas přidán 20. 09. 2022
  • CppNow Website: www.cppnow.org​
    CppNow Twitter: @CppNow​
    ---
    Lightning Talk: Initialisation in Modern C++ - Timur Doumler - CppNow 2022
    ---
    Timur Doumler presents this CppNow lightning talk on "Initialisation in modern C+-+" at the CppNow 2022 C++ conference held in Aspen, Colorado.
    ---
    Timur Doumler
    ---
    Videos Filmed & Edited By Bash Films bashfilms.com/
    CZcams Channel Managed By Digital Medium Ltd: events.digital-medium.co.uk
    #Boost​ #Cpp​ #CppNow​
  • Věda a technologie

Komentáře • 7

  • @yanushkowalsky1402
    @yanushkowalsky1402 Před rokem +5

    what we need is more types of parenthesis initialization

  • @pouet843
    @pouet843 Před rokem +12

    When you can find 10 different ways of initializing a bloody variable in a language, how are you supposed to correctly teach it to students... I hope one day the committee will decide to break compatibility with previous versions so we can have a unique and clear way of working and learning. Because at this point, this is a total non-sense.

  • @amber1862
    @amber1862 Před rokem +1

    Love this man. Such a great educator, especially in the world of audio.

  • @DiegoHavenstein
    @DiegoHavenstein Před rokem +3

    thing of nightmares

  • @BrunoSantosX
    @BrunoSantosX Před rokem

    But the modern C++ initializing is failing on Xcode 14.0 with -std=c++20 or -std=gnu++20 :(

  • @7alfatech860
    @7alfatech860 Před rokem

    C++ initialisations is just getting totally out of hand. Can we please have even more ways to add inscrutable errors to our programs?

  • @4otko999
    @4otko999 Před 8 měsíci +1

    imo this reptiloid syntax int x{0} was a mistake and should not have been allowed. compiler should just optimize away assigning in int x = {}. those gimmicks always bite in the butt, c++ should have went with how other languages do that and don't reinvent the wheel. i'm absolutely OK if c++26 would deprecate all that "fancy" initialization that should never have been used in the first place. yeah, yeah, breaking changes, whatever. just print a warning when something unwanted is used.