Yuya Tanaka

It is because current version of this library does not use NamedValueChecker implemented on connection (and only use statement's one). #61 is fix for that. But in https://github.com/go-sql-driver/mysql/pull/1090 it is...

> Because sqldb-logger log interaction with *sql.DB as-is. To my understanding, this is sqldb-logger's side issue: the cause of this issue is that sqldb-logger's logic is different from how golang...

It is catched here. https://github.com/jaredpalmer/formik/blob/f117c04738ed218b5eb8916d7189e0849962d50d/packages/formik/src/Formik.tsx#L841 I want to handle promise rejection error to send it sentry or etc. `Formik.errorHandler = () => ...` or something else?

I got this error today: `TypeError: Cannot read property 'callAsync' of undefined` with webpack watch https://github.com/Realytics/fork-ts-checker-webpack-plugin/issues/170 webpack: 4.12.0 speed-measure-webpack-plugin: 1.2.3 fork-ts-checker-webpack-plugin: 0.5.0

FYI: procps (`free` command) is going to support MemAvailable. https://gitorious.org/procps/procps/commit/ba6396f886f1a9911221e1c7c4b66dc75acb6948

Package name is changed, use below snippet for 2.0.0+. ``` -keep class codetail.graphics.drawables.** { *; } ```

Region is exposing mutable NSCalendar instance to public, so **Region is mutable**. Is it also expected..? ``` swift public let calendar: NSCalendar! ```

I worry about thread and mutability because I want to cache default Region object to memoize NSCalendar object. New Region is created on each `nsDateInstance.add(...)` and it impacts performance.

Yes, `let calendar` cannot be changed. But NSCalendar itself is mutable class. For example, locale can be changed by `region.calendar.locale = ...` from outside of the library.

> https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/Multithreading/ThreadSafetySummary/ThreadSafetySummary.html NSTimeZone is thread safe according to the document. > struct that mimics the data model of NSCalendar I agree with this, because only public constructor `Region(calendarName:, timeZoneName:, localeName:)`...