ju1ius

> Again, I do understand the issue with autocomplete - i'm just not convinced the control of the filename is the answer to that. I think everybody here can agree...

Yeah, inheritance doesn't work ATM...

> none of the exception properties weren't initialized, the exception will always not have a backtrace I think the reason why there's no backtrace is that you might be trying...

You would have an error if the exception is **thrown** without a stack frame, not when constructing the exception object, see https://heap.space/xref/php-src/Zend/zend_exceptions.c?r=45e224cf#244.

> throwing it doesn't result in an error, if you try the code above an call do throw from_bar() in PHP, it would throw the exception, but with no trace....

There's a discord channel that is more appropriate for these kind of lengthy discussions: https://discord.com/channels/115233111977099271/829877152048349266

IMO not exposing the actual _value_ is not that much of an issue. Exposing a public constant in an api is meant to provide an abstraction over a value that...

If you're going to make repeated calls to a method, the correct (and tedious) way is to fetch the `zend_function` pointer from the [get_method object handler](https://www.phpinternalsbook.com/php7/classes_objects/object_handlers.html#c.get_method), then use [zend_call_known_function](https://docs.rs/ext-php-rs/latest/ext_php_rs/ffi/fn.zend_call_known_function.html). This...

Yes, it is quite annoying that the library does not expose zval type flags in an idomatic way... Meanwhile: ```rust use ext_php_rs::{flags::ZvalTypeFlags, types::zval::Zval}; fn zval_type_flags(value: &Zval) -> ZvalTypeFlags { unsafe...

Thinking about it, it should look more like : ```rust #[php_class(field_case = "snake", method_case = "camel", constant_case = "upper")] struct Foo; ``` This would ease the burden of verbose repeated...