Skip to content

Instantly share code, notes, and snippets.

View uvsmtid's full-sized avatar

Alexey Pakseykin uvsmtid

  • Singapore
View GitHub Profile
@uvsmtid
uvsmtid / code-style.java.new-lines.IntelliJ-2017.1.3-OLSD.md
Last active July 29, 2017 08:41
Inconsistently missing options for auto-formatting / Wrapping and Braces / Java / Code Style / IntelliJ / 2017.1.3

These code style features to support OLSD: https://uvsmtid.com/obsessive-line-splitting-disorder-index/

This was submitted as this request to IntelliJ: https://intellij-support.jetbrains.com/hc/en-us/requests/1048712

Inconsistently missing options for auto-formatting / Wrapping and Braces / Java / Code Style / IntelliJ / 2017.1.3

1. "Extends/Implements list" section misses option "New line after implements".

Such option would be equivalent to "New line after (" under "Method declaration parameters" section.

This note demonstrates need for alternate approach to extend pillar data.

Example

  • Salt Master config /etc/salt/master:

    pillar_roots:

base:

// This is a C++ port from Java of Martin Thomson's code to demonstrate
// write combining buffers.
// See: http://mechanical-sympathy.blogspot.sg/2011/07/write-combining.html
#include <iostream>
#include <limits>
#include <chrono>
const int ITERATIONS = std::numeric_limits<int>::max();
@uvsmtid
uvsmtid / salt_pillars_vs_grains.md
Last active March 5, 2024 20:45
Salt Grains vs Pillars

Salt Grains vs Pillars

Both grains and Pillars define input data to parameterize [Salt][1] states.

Depending on the purpose of data, one should make a choice to put it in one place or another.

NOTE:

  • This doc focuses on practical differences between Grains and Pillars for [default use case][2] only.
  • It is not about everything what is possible.