Stefan Behnel wrote:

No. "@cython.cfunc" declares a function or method as a pure C function,
without a Python interface to it, and for methods, it only applies to
extension types and not regular Python classes.

It's interesting that Cython allowed you to set it on the "__iter__" method
which cannot, in fact, be a C method because it's one of Python's special
methods. We s

From conan-io/conan#6896

The information stored in the editable_packages.json in the Conan cache contains only the path to the folder where the recipe is. As a consequence, if the file is not called conanfile.py, Conan will fail to locate the recipe.

The Khronos reference page contains description of parameters and description of the behavior for every function. Wouldn't it be possible to add doc comments for the functions, so IDE can show it? I understand the function description is a bit cumbersome, as one description is usually related to multiple functions with similar functionality, however parameters description would help a lot.
I am c

• incremental CTU (on the fly CTU with skip files) feature usage configuration, limitations when ready
• web UI usage
  • how to compare the previous (marked by tag, use the date filter) results of two runs (same run?)
• more simple and advanced use case examples
  • CI job for a quality review (check for high severity results and fail the job if any)
  • usage of the upcoming f

Expecting: "${gadgetDir}/vscode-cpptools/debugAdapters/bin/OpenDebugAD7.exe"
Actual: "${gadgetDir}/vscode-cpptools/debugAdapters/OpenDebugAD7" -- which is a bash script.

Currently when choosing any of the other output formats it's not possible to get the text report printed to stdout or even a file.

I've tried the following, but neither work.

$ gcovr --sonarqube coverage.xml --output
usage: gcovr [options] [search_paths...]
gcovr: error: argument -o/--output: expected one argument
$ gcovr --sonarqube coverage.xml --output -
(WARNING) --output='-' op

Hi,

It's possible that I'm just misunderstanding the documentation here, but in the docs it says that using the --test flag on the build command wil make cget "try to run the check target" after building.

Does this mean that it will try to execute the resulting executable that is generated from building the check target? If so, this does not seem to happen.

Or am I misunderstand

Hi,

I'm trying to use the RQ kernel. First of all, in its help file I don't understand if I should put alpha or log_alpha as an input parameter. If the latter, is the logarithm natural or base 10?

Second of all, I checked R&W, and their formula 4.19 is not exactly the same as the one in george. Is it an issue, or are they mathematically equivalent?

Thanks in advance

Cheers

In the README it states that in your .clang file you want to point to a project specific compilation database you need to specify it like so:

compilation_database = "<path to compilation_database>"

Actually you need to specify to the directory that contains it, rather than to the database itself.
i.e. if the file sits at catkin_ws/build/compile_commands.json your .clang file should s

The documentation for the 'cflags' feature in the latest Boost Build docs says:

"For cflags that is both the C and C++ compilers, for cxxflags that is the C++ compiler"

but this is not reflected in the common.handle-options rule, which has 'cflags' being set for the toolset's 'compile.c' rule rather than for the toolset's 'compile' rule, while the 'compileflags' feature, which is no longer d

Write a class method recursivePrint(int count) of a class Recursion which prints "z y x w "
on the first line, "z y x " on the second line, ..., "z " on the fourth line by recursion if count is 4. If
count is n (n <= 26), n lines should be printed and the first line contains "z y x ...? ", where "?" is the
nth letter starting from "z". Note that there is a space after each letter.
Test it usin

Citing the doc: "The setup script is the centre of all activity in building, distributing, and installing modules using the Distutils."
source: https://docs.python.org/3/distutils/setupscript.html

For the Python community the setup.py file is a standard to know how to set up the environment just out of the box. Instead of running the right scripts in the order it would be better to have one kn

It would be nice if checkguard could warn about include guards using symbols are reserved for the compiler or standard library. It's an easy thing to forget about when picking your guard pattern. I put a reminder in the docs, but it wouldn't be hard to automatically check that.

Hi, giving a try to deoplete from YCM.
Can we have an example on how to work with the compile_commands.json. It says no config required... but where should the json be? It is generated by cmake in the build folder, #14 but it should be in the root of the project right? That should be noticed to the user.

Also, for a deoplete noob, do I need something else to say to deoplete? Something lik