Home » Blog » Categories »

Quick Q: Does access control matter for deleted constructors?

By Adrien Hamelin | Apr 9, 2018 02:58 PM | Tags: c++11 advanced

Quick A: No

Recently on SO:

Does access control matter for deleted constructors?

Since it's overload resolution that makes the program ill-formed in this case, and not access specifiers (which are checked later), there is no difference in outcome. The compiler will always complain that a deleted function was picked.

But since the idiom before C++11 was "declare but not define a private copy c'tor to disable copying", I would consider it going along with the same idiom, and therefore favorable. You are using the "old slang" with some new language to describe the same thing, except better.

East End Functions--Phil Nash

By Adrien Hamelin | Apr 9, 2018 02:54 PM | Tags: community c++11

What's your opinion?

East End Functions

by Phil Nash

From the article:

There has been a recent stirring of attention, in the C++ community, for the practice of always placing the const modifier to the right of the thing it modifies. The practice has even been gifted a catchy name: East Const (which, I think, is what has stirred up the interest)...

Getting the Benefits of Strong Typing in C++ at a Fraction of the Cost--Vincent Zalzal

By Adrien Hamelin | Apr 6, 2018 01:56 PM | Tags: intermediate

Very interesting!

Getting the Benefits of Strong Typing in C++ at a Fraction of the Cost

by Vincent Zalzal

From the article:

Strong types promote safer and more expressive code. I won’t repeat what Jonathan has presented already in his series on strong types.

I suspect some people may find that the NamedType class template has a nice interface but is using a somewhat heavy machinery to achieve the modest goal of strong typing. For those people, I have good news: you can achieve many of the functionalities of NamedType, with a very simple tool. That tool is the humble struct...

Announcing code::dive 2018

By Adam Badura | Apr 5, 2018 11:34 PM | Tags: None

code::dive 2018 will be held in Wrocław (Poland), November 7-8, 2018.

Announcing code::dive 2018

by Adam Badura

From the article:

code::dive 2018, the fifth edition, will be held in Wrocław (Poland) on November 7-8, 2018.

Call for Papers is open until end of June 2018 -- register on the webpage.

C++Now Announces Closing Keynote by John Regehr

By Jon Kalb | Apr 5, 2018 07:30 PM | Tags: undefined behavior optimizations c++now

C++Now 2018 will be held in Aspen, May 6–11, 2018.

Closing Keynote Announced: John Regehr on Undefined Behavior and Compiler Optimizations

From the announcement:

John is a professor of computer science at the University of Utah, where his research group creates tools for making software more efficient and correct. One of his projects is Csmith, a tool that generates random C programs. Why? To test compilers, of course. Csmith has been used to find more than 500 previously unknown bugs in production-quality compilers.

John will share some of the insights he’s gained from his research into compilers.

He will discuss what undefined behavior means to the compiler and how compiler writers use it in surprising ways generate better code.

 

Parallel Coding: From 90x Performance Loss To 2x Improvement--"No Bugs" Hare

By Adrien Hamelin | Apr 5, 2018 02:20 PM | Tags: performance

Part 2!

Parallel Coding: From 90x Performance Loss To 2x Improvement

by "No Bugs" Hare

From the article:

In my previous post, we have observed pretty bad results for calculations as we tried to use mutexes and even atomics to do things parallel. OTOH, it was promised to show how parallel <algorithm> CAN be used both correctly and efficiently (that is, IF you need it, which is a separate question); this is what we’ll start discussing within this post...

Quick Q: Why does unary operator & not require a complete type?

By Adrien Hamelin | Apr 5, 2018 02:05 PM | Tags: intermediate

Quick A: It only need to take the address.

Recently on SO:

Why does unary operator & not require a complete type?

What if stru has overloaded operator&()?

Then it is unspecified whether the overload will be called (See Oliv's comment for standard quote).

How could unary operator & does not require a complete type?

That's how the standard has defined the language. The built-in address-of operator doesn't need to know the definition of the type, since that has no effect on where to get the address of the object.

One consideration for why it is a good thing: Compatibility with C.