Skip to content

Instantly share code, notes, and snippets.

Yufan Lou louy2

Block or report user

Report or block louy2

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@staltz
staltz / introrx.md
Last active Sep 18, 2019
The introduction to Reactive Programming you've been missing
View introrx.md
@TSiege
TSiege / The Technical Interview Cheat Sheet.md
Last active Sep 18, 2019
This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.
View The Technical Interview Cheat Sheet.md

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo since a gist is too difficult to maintain as an open source endevaor and there is no way to version it. I have updated below, but I will not be able to keep this one up to date so please checkout the repo instead. The below is just for some preservation for those who stumble across here.






\

@bvssvni
bvssvni / gist:9674632
Last active Apr 15, 2017
A Rust Chain Macro
View gist:9674632
//! Chain macro in Rust
//!
//! A typical usage is to avoid nested match expressions.
//!
//! Supports:
//! - Pattern matching
//! - Or expressions (A | B => ...)
//! - Guarded statements (x if <cond> => ...)
//! - Implicit else (requires all arms to return same type)
@aras-p
aras-p / preprocessor_fun.h
Last active Sep 16, 2019
Things to commit just before leaving your job
View preprocessor_fun.h
// Just before switching jobs:
// Add one of these.
// Preferably into the same commit where you do a large merge.
//
// This started as a tweet with a joke of "C++ pro-tip: #define private public",
// and then it quickly escalated into more and more evil suggestions.
// I've tried to capture interesting suggestions here.
//
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,
View weasel.custom.yaml
#weasel.custom.yaml
patch:
"preset_color_schemes/Solarized_Lite":
author: "五磅兔 zcunlin@foxmail.com, based on Aben's 曬經石\solarized_Rock, original artwork by ethanschoonover‘s solarized"
back_color: 0xe3f6fd #底色
border_color: 0xd5e8ee #边框色
candidate_text_color: 0x837b65 #候选项颜色
comment_text_color: 0xd28b26 #编码提示颜色
hilited_back_color: 0xd5e8ee #编码底色
hilited_candidate_back_color: 0x98a12a #首选项高亮背景色
@dupuy
dupuy / README.rst
Last active Sep 2, 2019
Common markup for Markdown and reStructuredText
View README.rst

Markdown and reStructuredText

GitHub supports several lightweight markup languages for documentation; the most popular ones (generally, not just at GitHub) are Markdown and reStructuredText. Markdown is sometimes considered easier to use, and is often preferred when the purpose is simply to generate HTML. On the other hand, reStructuredText is more extensible and powerful, with native support (not just embedded HTML) for tables, as well as things like automatic generation of tables of contents.

You can’t perform that action at this time.