hryniuk

#ifndef OP_HPP
#define OP_HPP

#include <array>
#include <cmath>
#include <functional>

template <typename T1, typename T2, typename T3=void>
using _RefFunTemplate = std::function<T3(T1, T2)>;

hryniuk

Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118

Your problem with Vim is that you don't grok vi.

You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).

The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:

0 go to the beginning of this line. y yank from here (up to where?)

hryniuk

import aiohttp
import asyncio

async def l(event, q):
    while True:
        # ok, I'm ready
        event.set()
        # get value to process
        a = await q.get()
        # process it

hryniuk

#include <iostream>

template<typename T, typename S>
struct Citizen
{
    Citizen(T k, S l) : k_{k}, l_{l} {}
    T k_;
    S l_;
};

hryniuk

#include <iostream>
#include <limits>

int main()
{
    int a = std::numeric_limits<int>::min();
    std::cout << a << "\n";
    std::cout << a * -1 << "\n";
}

hryniuk

(You can comment here.)

Here I'm trying to understand what happens when I run

./hello

#include 

hryniuk

things I don't know

I took this list from What CS majors should know.

I think it is fun to list things I don't know so I did it =D. I actually found it to be a cool exercise -- maybe I should do a fun graphics project and learn about Open GL!

i wrote this because, while i think the things on this list are potentially worth knowing, and I actually think it's an awesome list of project ideas as well as good food for thought for people developing CS curricula (many of the things I don't know are great exercises!) -- I thought it was really weird to say that every CS student should know all of them. I have a CS degree and I learned very few of the things I do know inside my degree.

I classify "do know" as anything that I have a reasonable grasp of or at least some basic experience with -- the kind of experience I'd expect a CS student to be able to get. If I say I don't know something, it means either I know pretty much nothing about it (for "gr

hryniuk

class LogCountDescriptor:

    def __init__(self, log_count=0):
        self.log_count = log_count

    def __get__(self, obj, type=None):
        print("log from {}".format(obj))
        self.log_count += 1
        return self.log_count

hryniuk

#include <iostream>

struct A
{
    A() { std::cout << "default\n"; }
    A(std::string a) { std::cout << "string\n"; }
};

int main()
{

hryniuk

import functools

class B():
    def __init__(self, n):
        self.n = n
    def __call__(self):
        print(self.n)

class A():