HackerTube 中文?

Clasp: Common Lisp using LLVM and C++ for Molecular Metaprogramming

Google TechTalksYouTube ↗

Further reading 1

Who pays the cost an interface hides? →Zero-cost abstractions, a different allocator, concurrency inside a component: an interface spares callers the details, but time, memory and coordination costs do not vanish. They change hands.This video helps answer · Once Lisp can generate machine code, what does it still need to call an existing C++ function?

Caption notes

In this 2015 Google Tech Talk, Christian Schafmeister explains the design of Clasp. He wanted Common Lisp macros for generating code and access to existing C++ libraries. He describes compilation and language interoperability separately. Clasp’s compiler emits LLVM intermediate representation, which LLVM lowers to machine code. The binding library generates wrappers at compile time for C++ functions exposed to Lisp. In the Q&A he identifies debugging code produced by macro expansion as an open problem at the time.

Archived captions (transcription method unspecified) ↗
Original passages · 2
implemented a new Common Lisp that uses LLVM as the backend.
Clasp: Common Lisp using LLVM and C++ for Molecular Metaprogramming · ▶ 20:24–20:31
and it builds the wrapper function at compile time.
Clasp: Common Lisp using LLVM and C++ for Molecular Metaprogramming · ▶ 39:58–40:01

Hacker News comments

View original on HN ↗