Léopold Durand

Léopold Durand OSB (1666–1746) was a French architect.

Bibliography

Dom Durand was born in Saint-Mihiel (Lorraine) in 1666. He studied law and architecture, after which he went te become a member of the order of Saint Benedict (1702).

Works

  1. Traité historique des eaux et baines de Plombières (1748)
  2. Recueil sur l’architecture
  3. Plans de diverses églises
  4. Description des temples de Chine
  5. Termes de l’art et architecture militaires
  6. De la construction des voûtes
  7. Jeux et combats des Grecs
  8. Recueil sur les théatres des Anciens
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.
gollark: If I remember right Go strings are just byte sequences with no guarantee of being valid UTF-8, but all the functions working on them just assume they are.
gollark: Oh, and the strings are terrible.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.