NOnoobermin·Feb 2, 2015Submission
113 points · Open discussionklmr
named-operator
C++2014–2015
klmr / named-operator
named-operator
Named operators for C++
3Distinct people
3Mentions
0Explicit recommenders
513GitHub stars
What to know before exploring
What it is
Named operators for C++
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month3 dated mentions
Observed mentions: 2014-03-15 18:47:12 UTC to 2015-02-02 05:45:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Mar 2014 | 2014-03-01 00:00:00 UTC | 2014-04-01 00:00:00 UTC | 1 | 0 | 1 |
| Apr 2014 | 2014-04-01 00:00:00 UTC | 2014-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2014 | 2014-05-01 00:00:00 UTC | 2014-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2014 | 2014-06-01 00:00:00 UTC | 2014-07-01 00:00:00 UTC | 1 | 0 | 1 |
| Jul 2014 | 2014-07-01 00:00:00 UTC | 2014-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2014 | 2014-08-01 00:00:00 UTC | 2014-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2014 | 2014-09-01 00:00:00 UTC | 2014-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2014 | 2014-10-01 00:00:00 UTC | 2014-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2014 | 2014-11-01 00:00:00 UTC | 2014-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2014 | 2014-12-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2015 | 2015-01-01 00:00:00 UTC | 2015-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2015 | 2015-02-01 00:00:00 UTC | 2015-03-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
3 sourcesNot relevant in this case, but you may find this interesting (assuming you haven't seen it already): https://github.com/klmr/named-operator.
In Show HN: C++11 immutable string> If in is an operator and overloaded by std::vector, then it's easy to implement.
However, searching a `std::vector` is not really part of its implementation. So, requiring every single range to overload an operator for trivial searching is not good, especially since there are only a few containers that have non-trivial searching.
Instead, the range-based find could be specialized for containers that have non-trivial searching instead(perhaps it calls a `.find` method if available otherwise it does trivial searching).
In [Linq](http://pfultz2.github.io/Linq/), the find is specialized for mapped containers and for strings(it doesn't check for a `.find` method since that can't be done on msvc). So you can search a `std::vector` like this:
std::vector<int> v = { ... };
auto it = v | linq::find(123);
And you can also search the keys
Read the rest
of a map like this:
std::map<int, std::string> m = { ... };
auto it = m | linq::find(123);
Plus, it has a contains function, so you can do this:
if (v | linq::contains(123))
Or this:
if (m | linq::contains(123))
There really is no need for a new operator just for this, since a function will suffice. However, if you really inclined to this, you could always write your own [named operator](https://github.com/klmr/named-operator)(although I don't know if it would become standard):
if (123 <in> v)