Yauheni Khnykin

File `Release/src/pch/stdafx.h` contains following headers: ``` #include "boost/thread/condition_variable.hpp" #include "boost/thread/mutex.hpp" ``` which are not used. Instead of them `std::thread` and `std::condition_variable` are used all over the code (at least I...

Line breaks in results

3

We connected gmock framework to XCTest and it represents error with line breaks and sometimes with call stack, for example: > AngleTest.cpp:25: error: -[Angle::angle_values_are_consistent] : > Expected: angle_deg + 100...

Use std::string_view instead of std::string when string constant are generated

2

Assuming next declaration in lime: ``` struct Foo { const BAR: String = "bar text" } ``` Gluecodium generates struct with static const std::string fields: ``` struct Foo { static...

Dart-related failures in CMake unit tests

1

While running Xcode-related unit tests for Xcode I met linking issues in two tests: ``` 19: Undefined symbols for architecture x86_64: 19: 19: "_library_execute_finalizer", referenced from: 19: _library_unit_test_MainBar_register_finalizer in object.module.only.main_main_ffiglue.o...

Investigate and generate CMake documentation (HTML) on CI, related documentation: https://github.com/Kitware/CMake/blob/master/Help/dev/documentation.rst

Sometimes COMMON code is missing and not regenerated

2

I didn't catch yet how it happen, but sometimes COMMON code is removed probably by Gluecodium and not generated again which leads to compilation error in C++. How to reproduce:...

Currently many options must be aligned to generate compilable code when few few modules depend (in lime files) on each other. It leads sometimes to hardly understandable issues with generated...

Make custom struct's constructors in C++ consistent with the rest of code.

1

Consider next struct in lime: ``` struct Foo { field1: String field2: String = "predefined" constructor make(field1: String) constructor make(field1: String, field2: String) } ``` Custom constructors should check parameters...

The most often construction in our documentation looks like: `{@Java Interface}{@Swift Protocol}{@Dart Abstract class}`. We repeat it for many classes and actually it contains an error, because it must include...

Add support for disposable types

1

Consider the next use case: I have class Foo described in lime. I create object of class Foo which acquire some non-shareable resources. I want to create second instance of...