[JAVA] A list of complacency articles on language specifications that probably won't help you in programming directly

What's this

This is a personal note.

Carefully selected from 7 years and 8 months' worth of articles (as of September 2019) written in the Hatena blog "yohhoy's diary", "Useful for most people. This is a list of "articles that I did my best to research and write, although I wouldn't stand up." With a brief comment.

C++ -same_as Concept and Symmetric Subsumption Idiom --Concept design idiom. Easy to use, hard to make. -Concept constraint expression inclusive relation and overload resolution --A small part of the abyss related to the new C ++ 20 concept. C ++ I don't know. -Strict stream input / output and evaluation order rules --The story of the language specifications improved in C ++ 17. The details are difficult, but the conclusion is simple. -std :: launder function --A mysterious function added to the C ++ 17 library. C ++ Mutsukacine. -Evaluation order rule of i = i ++ + 1; --A story about language specifications adjusted in C ++ 17. Higher maniac degree. --shared_ptr reference counting and data race --C ++ 17 A strange change in the library started. Multithreading was too early for humanity.

C

Java -Type inference and infinite type --Java compiler is great. Type inference is not a human task.

Rust -Dangerous type conversion: & T → & mut T --Listen to what the Rust compiler says. unsafe Seriously unsafe.

Objective-C -Objective-C atomic attribute property and inter-thread synchronization --The triple darkness of language specifications, compiler optimization, and memory model. Why did you write such an article?

Recommended Posts

A list of complacency articles on language specifications that probably won't help you in programming directly
A program that counts the number of words in a List