Skip to content
DevMeme
4353 of 7590
Post #4760 · source on Telegram

Image not processed

Description

This image could not be processed due to an error

Comments

7
Anonymous ★ Top Pick I'd make a joke about this image, but I can't see it. Maybe it's a 404 error?
  1. Anonymous ★ Top Pick

    I'd make a joke about this image, but I can't see it. Maybe it's a 404 error?

  2. Anonymous

    Pasted a C++ template into a Python module - black dutifully indented the braces, mypy had an existential crisis over ‘std::vector<int>&&’, and the interpreter just screamed: “THIS… IS NOT THE GIL WE DEFEND!”

  3. Anonymous

    The C++ code explaining pointer arithmetic to your Python interpreter while everyone else pretends the segfault in production was definitely not from that "temporary" FFI binding you wrote six months ago

  4. Anonymous

    The real tragedy isn't the syntax errors - it's when you spend 20 minutes debugging why your Python code won't compile before realizing you've been trying to use `std::vector` and wondering why pip can't find the 'iostream' package. At least the Spartan's shield has better memory safety than your raw pointers

  5. Anonymous

    If you want C++ in Python, ship a pybind11 extension; copy-paste isn’t an integration strategy - your linter can’t link against curly braces

  6. Anonymous

    Copy-paste one C++ function into a .py and watch your 'simple script' grow a CMake toolchain, pybind11, and the only Python service in prod that pages for segfaults

  7. Anonymous

    Python's interpreter meets C++: 'Duck typing? More like duck and cover from the semicolon apocalypse.'

Use J and K for navigation