Describe the bug
When I use closure for format as written in documentation,
an error Warning: date() expects parameter 1 to be string, object given occurs.

To Reproduce

// Warning: date() expects parameter 1 to be string, object given
new Timestampable([
            'beforeCreate' => [
                'field

I think this sould be documented here: https://docs.zephir-lang.com/0.12/en/operators#empty
Because there is absolutely nothing in the "empty" documentation that suggest this different behaviour.

Originally posted by @colorvamp in phalcon/zephir#917 (comment)

In README.md

If you execute untrusted JavaScript code, make sure to use V8 version 6.4.388.18, 6.5.143 or higher. See notes on untrusted code mitigations for further details.

However, the latest version of v8js requires libv8 version 6.9, so this note should mention it only needs to be checked when building older releases of v8js (or be removed)

我的php.ini 配置如下：
seaslog.default_template = "%T | %L | %I | %H | %P | %Q | %t | %M"

还有一个问题:
mac 下貌似不能写入其它级别的log 只能写入 EMERGENCY 级别的错误，
我的配置是

;;记录日志级别，数字越大，根据级别记的日志越多。
;;0-EMERGENCY 1-ALERT 2-CRITICAL 3-ERROR 4-WARNING 5-NOTICE 6-INFO 7-DEBUG 8-ALL
;;默认8(所有日志)
;;
;; 注意, 该配置项

I had compile and install opencv(4.1.1) with it's module opencv_contrib(4.1.1) yesterday. when I compile phpopencv today ,there's an error appeared that "make:***[opencv.lo] error 1",

Following is the whole infomation :

`
/usr/local/include/opencv4/opencv2/core/mat.hpp:2070:12: error: expected ‘,’ or ‘...’ before ‘&&’ token
Mat(Mat&& m);
^
/usr/local/include/opencv4/open

IMHO, for an open source project, the community environment is the most important thing. So please make sure, every people who are interesting in your repository, know who you are, and how to contact you.

So at least provide your information for contacting you. At least, if you want to make things easier, you can use Skywalking's gitter room, google maillist, QQ group, etc. **Bottom line is, pe

From @tamaranga on February 1, 2014 9:39

It's impossible to create class:

class HTML {
}

and method:

class Test {
      public function HTML() {}
}

Maybe it is not so difficult to allow such capitalized names or describe this limitation in docs. Currently it's just "ParseException: Syntax error", that is not very obvious.

See serializeAttributes() where we mangle the JSON attributes in order to provide additional safety against transformations that WordPress might further take.

That is, it's not just "spec JSON" even though it should still be spec compliant. Also, I don't think we've specifically chosen RFC 7159 as our implementa

The current docs on this don't go in to any detail about what the various available approaches are to get these right.