This is a gist repository for some external configs for subconverter, you can use the raw address of the following INIs to generate a specified set of rules, groups and/or scripts.
| #ifndef lazy_memory_h | |
| #define lazy_memory_h | |
| #include <stdint.h> | |
| #include <string.h> | |
| #define CacheLine 64 | |
| #define WordSize (sizeof(uint64_t) * 8) // 64 (bits) | |
| #define AlignN(s, n) (( s + n - 1) / n * n) |
调查目的:了解当前各基于TLS的协议方案中ClientHello的指纹独特性。理论背景见 https://arxiv.org/abs/1607.01639 。
指纹数据库:
(利益相关:我是这个的作者)
| #ifndef __FINK_ENDIANDEV_PKG_ENDIAN_H__ | |
| #define __FINK_ENDIANDEV_PKG_ENDIAN_H__ 1 | |
| /** compatibility header for endian.h | |
| * This is a simple compatibility shim to convert | |
| * BSD/Linux endian macros to the Mac OS X equivalents. | |
| * It is public domain. | |
| * */ | |
| #ifndef __APPLE__ |
| - (UIImage *)dynamicImage | |
| { | |
| UITraitCollection *const baseTraitCollection = /* an existing trait collection */; | |
| UITraitCollection *const lightTraitCollection = [UITraitCollection traitCollectionWithTraitsFromCollections:@[baseTraitCollection, [UITraitCollection traitCollectionWithUserInterfaceStyle:UIUserInterfaceStyleLight]]]; | |
| UITraitCollection *const purelyDarkTraitCollection = [UITraitCollection traitCollectionWithUserInterfaceStyle:UIUserInterfaceStyleDark]; | |
| UITraitCollection *const darkTraitCollection = [UITraitCollection traitCollectionWithTraitsFromCollections:@[baseTraitCollection, purelyDarkTraitCollection]]; | |
| __block UIImage *lightImage; | |
| [lightTraitCollection performAsCurrentTraitCollection:^{ | |
| lightImage = /* draw image */; |
The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).
My take-aways are:
-
You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.
-
Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse
$ sudo yum -y update
$ sudo yum -y install golang
$ sudo yum -y install gmp-devel
$ sudo yum -y install git
$ git clone https://github.com/ethereum/go-ethereum
$ cd go-ethereum/
$ make geth
$ ls -al build/bin/geth
| // Similar to defer in Swift | |
| #define pspdf_defer_block_name_with_prefix(prefix, suffix) prefix ## suffix | |
| #define pspdf_defer_block_name(suffix) pspdf_defer_block_name_with_prefix(pspdf_defer_, suffix) | |
| #define pspdf_defer __strong void(^pspdf_defer_block_name(__LINE__))(void) __attribute__((cleanup(pspdf_defer_cleanup_block), unused)) = ^ | |
| #pragma clang diagnostic push | |
| #pragma clang diagnostic ignored "-Wunused-function" | |
| static void pspdf_defer_cleanup_block(__strong void(^*block)(void)) { | |
| (*block)(); | |
| } | |
| #pragma clang diagnostic pop |
| /* Copyright 2017 rot256 | |
| * | |
| * Permission is hereby granted, free of charge, | |
| * to any person obtaining a copy of this software and associated documentation files (the "Software"), | |
| * to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, | |
| * and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: | |
| * | |
| * The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. | |
| * | |
| * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, |
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages