profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Y--/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

astro/node-expat 362

libexpat XML SAX parser binding for node.js

hmalphettes/elasticsearch-http-basic 3

HTTP Basic Authentication for Elasticsearch

Y--/js-xlsx 1

XLSX / XLSM / XLSB (Excel 2007+ Spreadsheet) parser and writer

hmalphettes/elasticsearch-native-script-example 0

Example of Native Script Plugin for Elasticsearch

hmalphettes/node-elasticsearch-client 0

A client written in node for elastic search

Y--/cling 0

Cling is an interactive C++ interpreter, built on top of Clang and LLVM compiler infrastructure.

Y--/core 0

:house_with_garden: Open source home automation that puts local control and privacy first

Y--/debug.hxx 0

Header only debug module for c++11

CommitCommentEvent
CommitCommentEvent

push eventsutoiku/cling

Oksana Shadura

commit sha d1c279a0755bbe061553596ac76e4e2d9cce91e5

Update minimal CMake version in favour of advances features it offers (#8336) * Update minimal CMake version in favour of advances features it offers * Remove workaround for FindDoxygen (cmake < 3.13) * Remnove workaround for cmake < 3.14 to able to report issue directly to stdout * Remove workaround for CMake < 3.14 when Ninja 1.9.0 builds static libraries twice * Remove other CMake hack from multi-python ROOT builds * We are using 3.16 as a min CMake version and REGEX is definitely available in this version * Remove code used to search Python2/Python3 with <= CMake 3.14

view details

Vassil Vassilev

commit sha 03e02c57bb3b4eb2a8b091d5a16d1490d0438192

Fix regression in #pragma cling add_library_path(). This regression was introduced by root-project/root@561e905b where we stopped iterating, on every lookup, over the -L paths passed at start up. This patch adds the path to the search paths of the DynamicLibraryManager rather than to the invocation options.

view details

Vassil Vassilev

commit sha 55a4e89b3bec0837ff0482ff41d737596c491c26

Fix ROOT-10484 by implementing dyld support for RPATH. Some libraries are layered can depend on other libraries on a private paths. That is, libA can depend on libB which is neither on the LD_LIBRARY_PATH nor on a known system path. The posix linker injects "variables" such as @rpath which is expanded at link time to resolve the libraries on a relative path. Prior to this patch, cling's Dyld-based symbol resolution could not trace down such cases causing failures in symbol resolution when a symbol is only defined in libB (a private library). This patch implements the basic posix linker substitutions allowing cling's Dyld-based symbol resolution implementation to follow more closely the linker rules. Kudos Alexander Penev (@alexander-penev).

view details

Vassil Vassilev

commit sha d36bfe15e486d4036e78afa3d8c5077ea55b194e

Ask for the real path in any case.

view details

Vassil Vassilev

commit sha 276a46bcfabf3bd2e2ec19f6a8318f37cbc29728

Silence warning ignoring return value of readlink.

view details

Axel Naumann

commit sha 10180ae79f7591d69c2f362cebe63aabe2ef887d

On Win, do not always-append to cling-compiledata.h.in: Before, cling-compiledata.h caused ``` interpreter\cling\lib\Interpreter\cling-compiledata.h(6,1): warning C4005: 'CLING_UCRT_VERSION': macro redefinition interpreter\cling\lib\Interpreter\cling-compiledata.h(3): message : see previous definition of 'CLING_UCRT_VERSION' ``` due to it containing ``` #define CLING_INCLUDE_PATHS "" #define CLING_UCRT_VERSION "" #define CLING_INCLUDE_PATHS "" #define CLING_UCRT_VERSION "10.0.19041.0" ```

view details

Baidyanath Kundu

commit sha 8e950be75d5d636a34ef0b1a4341d04cfefc1d33

Bump clad version to v0.9. This new release includes some improvements: * Extended array support * Add cmake variables to control the locations where find_package discovers LLVM and Clang: `LLVM_CONFIG_EXTRA_PATH_HINTS` and `Clang_CONFIG_EXTRA_PATH_HINTS` respectively. See more at: https://github.com/vgvassilev/clad/blob/v0.9/docs/ReleaseNotes.md

view details

Vassil Vassilev

commit sha d78d1a03fedfd2bf6d2b6ff295aca576d98940df

Fix building ROOT with external llvm. Fixes #8141.

view details

Javier Lopez-Gomez

commit sha 41f3ed6c97916ac820a035085311c9fa7e48601e

MetaLexer: return `/*` and `*/` as tokens; added `ReadToEndOfLine()` This commit includes the following changes to MetaLexer: - Update `MetaLexer::Lex()` to return `/*` (tok::l_comment), `*/` (tok::r_comment), and `<` (tok::less) as tokens. - Added `MetaLexer::ReadToEndOfLine()` function: consume input until `\r` or `\n`. - Added `MetaLexer::RAII`, a RAII object that saves/restores the current position.

view details

Javier Lopez-Gomez

commit sha e2d44c31a33a2633ba0c2d29f06924cc8f6615a4

Rewrite of `InputValidator::validate()` Replace implementation of `InputValidator::validate()` by simpler, more maintainable code that also fixes ROOT-9202. The previous implementation was unable to properly handle line continuation after ',' or '\'. Specifically, it skipped over non-punctuation tokens, entering continuation mode even if ',' or '\' were not the last tokens in the input, e.g. `int a, b` or 'int a \ b'. Fixes ROOT-9202.

view details

Javier Lopez-Gomez

commit sha a8a3db4611fcc2838c2f30dcd385d9dd9148d70c

Cleanup MetaLexer; remove unused `LexPunctuatorAndAdvance()`

view details

Javier Lopez-Gomez

commit sha 8d983402999fea39fd687f428e4421c2d6a5f149

`InputValidator::validate()`: add test against ROOT-9202

view details

Javier Lopez-Gomez

commit sha dd1a74f009ca1840f4ab093fc866172bb202060d

Enable replacement of the default diagnostic consumer These changes enable the replacement of the default DiagnosticConsumer provided by CIFactory. Concretely, two member functions have been added to the Interpreter class: - replaceDiagnosticConsumer(): replaces the default CIFactory-provided DiagnosticConsumer. - hasReplacedDiagnosticConsumer(): returns whether the default diagnostic consumer has been replaced.

view details

Yves Le Maout

commit sha 4092fc5d892c5cf6efa480b326bb8451686f487e

[Experimental] Hack the IncrementalParser for our needs

view details

Yves Le Maout

commit sha 9d4e1dea4a9f5c69c105fcf8b9eb5f104aaabdbc

Return execution failed status if `executeInit` fails

view details

Yves Le Maout

commit sha a159ae80b733a91613c45c618ab26e71b884f68c

Don't compile demo

view details

Yves

commit sha d2a450c07582654abf6eabd34cbf209904a9d99b

Add our custom flags

view details

Yves

commit sha 118fcd2872babc465e541bdf0c60e505b824a8e6

Do not run tests

view details

Yves

commit sha 33e29f808b5fefe1be4be5a45cb17482a2ba89b0

Only compile for ubuntu 20.04

view details

Yves

commit sha 853ac5f8236c0ed2c32c0cf7cbae830f342f2ce1

Upload files

view details

push time in 7 days

pull request commentsutoiku/hubot-civ2

`getJiraLink` instead of `getPTLink `

Looks good for now, we should just keep an eye on it

p-lebouc

comment created time in 21 days

PullRequestReviewEvent

starteddatafuselabs/datafuse

started time in 23 days

startednlohmann/json

started time in a month

push eventsutoiku/hubot-civ2

Yves

commit sha 239e75641d1ec76f8146fd208584819cd62588bc

Improve error feedback

view details

push time in a month

push eventsutoiku/hubot-civ2

Yves

commit sha e71b8ad4d0aae3877f169b8e2e8f6c92dd87e413

Do not fail if we can't get description

view details

push time in a month

push eventsutoiku/hubot-civ2

Yves

commit sha cc70e2b534e18ee50eacbfbc493c510c5cde7019

Update bot

view details

push time in a month

push eventsutoiku/hubot-civ2

Yves

commit sha 9138466a75480c8b7e494489dccfa39b8dafeb1b

Update bot

view details

push time in a month

startedjlongster/absurd-sql

started time in a month

push eventY--/multipull

Yves

commit sha 102c2651b6aff8354dd5f4841f0e8f09629db3ab

Make sure we display the path in the error

view details

push time in 2 months

issue openedAssemblyScript/assemblyscript

Small code makes parser hang

<!-- Thanks for submitting an issue to AssemblyScript! Please take a moment to read the contributing guidelines linked below to get off to a good start 🙂 --> Hi!

If you try to paste this small snipped in the AS editor, and try to look at the WASM generated, the page becomes unresponsive:

export function foo() {
  if (idof<Foo>() == idof<Bar>) {
    baz();
  } else {
    `Some string`
  }
}

Note that:

  • the code is not correct (it is missing the parenthesis to call idof in idof<Bar>
  • if you remove the string template, from the else branch, the issue disappear
  • if you fix the idof call, the issue disappear

Let me know if you need any additional detail on this.

Thanks!

created time in 2 months

push eventsutoiku/cling

Yves

commit sha 39d90b27ec09b85e285a70f41346c14c3a0ce6c8

Remove noisy warning

view details

push time in 2 months

push eventsutoiku/cling

Yves

commit sha 1945c20bc7b4de872829d9babfa58da9bcceb6d5

Upgrade OS packages

view details

push time in 2 months

push eventsutoiku/cling

Vassil Vassilev

commit sha 682b7b9505e58a956e30cbc1ab03f43e41fab172

Reimplement HandleInvalidTagDeclDefinition without clang support. See https://reviews.llvm.org/D92248

view details

Vassil Vassilev

commit sha f3768a4c43b0f3b23eccc6075fa178861a002a10

Prepare for releasing cling v0.9

view details

Vassil Vassilev

commit sha 3e42a62f3f69f18324285b7c5c3837a68fa13040

Bump cling version to 1.0~dev.

view details

Axel Naumann

commit sha db2c5de3f22290a7ecd26b4b7e9688d2d0faaeea

Lifetime of MetaParser is that of its input: Before, MetaParser might have pointed to a StringRef whose storage was gone, see asan failure in roottest/cling/other/runfileClose.C below. This was caused by recursive uses of MetaParser; see stack trace below: the inner recursion returned, but as the same MetaParser object was used by both frames, the objects cursor now pointed to freed memory. Instead, create a MetaParser (and MetaLexer) object per input. That way, their lifetime corresponds to the lifetime of their input. ================================================================= ==529104==ERROR: AddressSanitizer: stack-use-after-return on address 0x7ffff3afd82a at pc 0x7fffea18df6d bp 0x7fffffff8170 sp 0x7fffffff8168 READ of size 1 at 0x7ffff3afd82a thread T0 [Detaching after fork from child process 529183] #0 0x7fffea18df6c in cling::MetaLexer::Lex(cling::Token&) src/interpreter/cling/lib/MetaProcessor/MetaLexer.cpp:58:11 #1 0x7fffea190d7c in cling::MetaParser::lookAhead(unsigned int) src/interpreter/cling/lib/MetaProcessor/MetaParser.cpp:89:15 #2 0x7fffea190bd5 in cling::MetaParser::consumeToken() src/interpreter/cling/lib/MetaProcessor/MetaParser.cpp:49:5 #3 0x7fffea191d4d in cling::MetaParser::isLCommand(cling::MetaSema::ActionResult&) src/interpreter/cling/lib/MetaProcessor/MetaParser.cpp:147:9 #4 0x7fffea1914dd in cling::MetaParser::isCommand(cling::MetaSema::ActionResult&, cling::Value*) src/interpreter/cling/lib/MetaProcessor/MetaParser.cpp:123:12 #5 0x7fffea191216 in cling::MetaParser::isMetaCommand(cling::MetaSema::ActionResult&, cling::Value*) src/interpreter/cling/lib/MetaProcessor/MetaParser.cpp:101:33 #6 0x7fffea14e5aa in cling::MetaProcessor::process(llvm::StringRef, cling::Interpreter::CompilationResult&, cling::Value*, bool) src/interpreter/cling/lib/MetaProcessor/MetaProcessor.cpp:317:24 #7 0x7fffe99b67b7 in HandleInterpreterException(cling::MetaProcessor*, char const*, cling::Interpreter::CompilationResult&, cling::Value*) src/core/metacling/src/TCling.cxx:2431:29 #8 0x7fffe99bde30 in TCling::Load(char const*, bool) src/core/metacling/src/TCling.cxx:3454:10 #9 0x7ffff7865f11 in TSystem::Load(char const*, char const*, bool) src/core/base/src/TSystem.cxx:1941:27 #10 0x7ffff7b8a0e3 in TUnixSystem::Load(char const*, char const*, bool) src/core/unix/src/TUnixSystem.cxx:2789:20 #11 0x7fffd78dd08b (<unknown module>) #12 0x7fffe9f8a5d9 in cling::IncrementalExecutor::executeWrapper(llvm::StringRef, cling::Value*) const src/interpreter/cling/lib/Interpreter/IncrementalExecutor.cpp:376:3 #13 0x7fffe9d73dc2 in cling::Interpreter::RunFunction(clang::FunctionDecl const*, cling::Value*) src/interpreter/cling/lib/Interpreter/Interpreter.cpp:1141:20 #14 0x7fffe9d6e317 in cling::Interpreter::EvaluateInternal(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, cling::CompilationOptions, cling::Value*, cling::Transaction**, unsigned long) src/interpreter/cling/lib/Interpreter/Interpreter.cpp:1391:29 #15 0x7fffe9d6c1fe in cling::Interpreter::process(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, cling::Value*, cling::Transaction**, bool) src/interpreter/cling/lib/Interpreter/Interpreter.cpp:819:9 #16 0x7fffea151826 in cling::MetaProcessor::readInputFromFile(llvm::StringRef, cling::Value*, unsigned long, bool) src/interpreter/cling/lib/MetaProcessor/MetaProcessor.cpp:507:22 #17 0x7fffe99b585b in TCling::ProcessLine(char const*, TInterpreter::EErrorCode*) src/core/metacling/src/TCling.cxx:2570:39 #18 0x7fffe99bbfee in TCling::ProcessLineSynch(char const*, TInterpreter::EErrorCode*) src/core/metacling/src/TCling.cxx:3496:17 #19 0x7ffff77203d3 in TApplication::ExecuteFile(char const*, int*, bool) src/core/base/src/TApplication.cxx:1608:30 #20 0x7ffff771ebdf in TApplication::ProcessFile(char const*, int*, bool) src/core/base/src/TApplication.cxx:1480:11 #21 0x7ffff771e385 in TApplication::ProcessLine(char const*, bool, int*) src/core/base/src/TApplication.cxx:1453:14 #22 0x7ffff7f8157a in TRint::ProcessLineNr(char const*, char const*, int*) src/core/rint/src/TRint.cxx:766:11 #23 0x7ffff7f802f0 in TRint::Run(bool) src/core/rint/src/TRint.cxx:424:22 #24 0x4ff96d in main src/main/src/rmain.cxx:30:12 #25 0x7ffff6e040b2 in __libc_start_main /build/glibc-YbNSs7/glibc-2.31/csu/../csu/libc-start.c:308:16 #26 0x41f35d in _start (asan/bin/root.exe+0x41f35d) Address 0x7ffff3afd82a is located in stack of thread T0 at offset 42 in frame #0 0x7fffe99b3d8f in TCling::ProcessLine(char const*, TInterpreter::EErrorCode*) src/core/metacling/src/TCling.cxx:2456 This frame has 21 object(s): [32, 56) 'sLine' (line 2462) <== Memory access at offset 42 is inside this variable [96, 104) 'R__guard2471' (line 2471) [128, 136) 'R__guard2488' (line 2488) [160, 176) 'interpreterFlagsRAII' (line 2491) [192, 240) 'result' (line 2511) [272, 276) 'compRes' (line 2512) [288, 312) 'mod_line' (line 2517) [352, 376) 'aclicMode' (line 2518) [416, 440) 'arguments' (line 2519) [480, 504) 'io' (line 2520) [544, 568) 'fname' (line 2521) [608, 632) 'ref.tmp' (line 2547) [672, 696) 'ref.tmp145' (line 2547) [736, 768) 'code' (line 2555) [800, 832) 'codeline' (line 2556) [864, 1384) 'in' (line 2559) [1520, 1552) 'ref.tmp176' (line 2562) [1584, 1600) 'agg.tmp' [1616, 1624) 'ref.tmp198' (line 2568) [1648, 1664) 'agg.tmp207' [1680, 1696) 'autoParseRaii' (line 2588) HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-use-after-return src/interpreter/cling/lib/MetaProcessor/MetaLexer.cpp:58:11 in cling::MetaLexer::Lex(cling::Token&) Shadow bytes around the buggy address: 0x10007e757ab0: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757ac0: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757ad0: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757ae0: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757af0: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 =>0x10007e757b00: f5 f5 f5 f5 f5[f5]f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757b10: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757b20: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757b30: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757b40: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 0x10007e757b50: f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe Left alloca redzone: ca Right alloca redzone: cb Shadow gap: cc ==529104==ABORTING at src/interpreter/cling/lib/MetaProcessor/MetaLexer.cpp:49 at src/interpreter/cling/lib/MetaProcessor/MetaParser.cpp:41 compRes=@0x7ffff3afd910: cling::Interpreter::kSuccess, result=0x7ffff3afd8c0, disableValuePrinting=false) at src/interpreter/cling/lib/MetaProcessor/MetaProcessor.cpp:314 input_line=0x7ffff3afd829 "#define XYZ 21", compRes=@0x7ffff3afd910: cling::Interpreter::kSuccess, result=0x7ffff3afd8c0) at src/core/metacling/src/TCling.cxx:2431 error=0x7fffd78cb0f4 <x>) at src/core/metacling/src/TCling.cxx:2591 sync=false, err=0x7fffd78cb0f4 <x>) at src/core/base/src/TApplication.cxx:1472 line=0x7fffd78c9000 "#define XYZ 21", error=0x7fffd78cb0f4 <x>) at src/core/base/src/TROOT.cxx:2328 from asan/roottest/cling/other/fileClose_C.so filename=0x6070000f0fd0 "asan/roottest/cling/other/fileClose_C.so", flag=257) at /home/axel/build/llvm/llvm-project/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:6270 at src/interpreter/cling/lib/Utils/PlatformPosix.cpp:118 permanent=false, resolved=true) at src/interpreter/cling/lib/Interpreter/DynamicLibraryManager.cpp:184 at src/interpreter/cling/lib/Interpreter/Interpreter.cpp:1444 T=0x0) at src/interpreter/cling/lib/Interpreter/Interpreter.cpp:1560 at src/interpreter/cling/lib/MetaProcessor/MetaSema.cpp:57 actionResult=@0x7ffff39532b0: cling::MetaSema::AR_Success)

view details

Vassil Vassilev

commit sha d466a98e302565e67f9a7e351c2982a96bc9f5f3

Consider only dll files to be shared libraries. This avoids problems where we consider other executables and object files as libraries and the dyld decides to scan them. Upon this we hit files opened by other processes and locked by the system (such as bootstat.dat :)) Thanks to Bertrand Bellenot for the diagnosis!

view details

Vassil Vassilev

commit sha 74f74a7d0b0de70f14ca81a1690d16fe52509278

Remove the include to IncrementalExecutor. This exposed a set of missing includes and constructors to destroy the backend passes.

view details

Vassil Vassilev

commit sha 561e905b246847cce31a4c2ef020c2fe7b2730f0

Use the dyld to show more meaningful message when a symbol is missing. The dynamic library manager's dyld can search a symbol in the library path. This patch uses that functionality to aid the 'unresolved while linking' diagnostics. Now we get: cling -L lib/ ****************** CLING ****************** * Type C++ code and press enter to run it * * Type .q to exit * ******************************************* [cling]$ extern int gErrorIgnoreLevel; [cling]$ gErrorIgnoreLevel IncrementalExecutor::executeFunction: symbol 'gErrorIgnoreLevel' unresolved while linking [cling interface function]! Symbol found in '/.../lib/libCore.so'; did you mean to load it with .L /.../lib/libCore.so ? [cling]$

view details

Javier Lopez-Gomez

commit sha 668dfdcc7ff8bc47ed9accb20b8639adcb7e80fb

cleanup `MetaSema.cpp` Additionally, this commit extends the behavior of `.x`. Specifically, it adds support for a list of function names whose execution will be tried in order. To be compliant with the old behavior, this list currently only includes an entry that matches the macro filename.

view details

Axel Naumann

commit sha fc5b3e6f16916789d0498a1bf3af216b44edcd31

Silence GCC 4.8 / CentOS7 warnings: cling/include/cling/Interpreter/LookupHelper.h:61:69: warning: missing initializer for member ‘std::array<const clang::Type*, 4ul>::_M_elems’ [-Wmissing-field-initializers] std::array<const clang::Type*, kNumCachedStrings> m_StringTy = {}; ^

view details

Axel Naumann

commit sha 3bd3ff18cb8557751fea83ccaa8fe4a3662a7596

Make sure required symbols are exported: and use a standard mechanism that plays well with -fvisibility. Given that several symbols now use declspec(dllexport), remove them from the ad-hoc cling_exports in ROOT's CMakeLists.txt.

view details

Axel Naumann

commit sha 07c60810596944903f0f74d2cc88e21241fa415f

Simplify visibility setting: Rather than string-replacing visibility, use the CMake interface. Do not set visibility in the ROOT case; ROOT can handle that just fine itself. ROOT actually does *not* need visibility=default, now that the few symbols that are required for using cling (apart from clingtest) are explicitly requested through attributes.

view details

Axel Naumann

commit sha bb143fbd2fcb469f744db9a4c9b52591acc218d2

Remove symbols explicitly exported through CLING_EXPORT.

view details

Mattias Ellert

commit sha 35259e725ad713fbf207aaddf9e2b19e09bf7f9a

Actually request the use of the large code model for ppc64/ppc64le Instead of erroring out with an assert.

view details

Axel Naumann

commit sha c385db1be7dfe1f03ff57e137ee4c5f622833251

Trust that GCC has `__attribute__` `visibility`: GCC 4.8 (which we support...) does not have __has_attribute. Fixes CentOS7 builds.

view details

Vassil Vassilev

commit sha 68b3b29a956c362ba8a7a5ceb1d7be8ce3b5a5a6

Bump clad version to v0.8. The new release includes some improvements: * Implement #pragma clad ON/OFF/DEFAULT to control regions where clad is active * Add getCode() interface for interactive use See more at: https://github.com/vgvassilev/clad/blob/v0.8/docs/ReleaseNotes.md

view details

Axel Naumann

commit sha 2d948ebcffb8d69bf0a393fe43fd80b85eeeb99d

Also fwd decl underlying type of using decls: Before, only the using decl itself was forward declared, causing undeclared identifiers in forward declaration code, as witnessed in https://github.com/root-project/root/issues/8499 Given the similarity of using and typedef, merge both into a single function, making sure both have the same featureset, and through that fixing this issue as a side-effect.

view details

Javier Lopez-Gomez

commit sha 4f714ac55bdea65556c6873524db25f3e9d4e772

Enable `-Wredundant-parens` Warn on redundant parentheses in declarators whose parsing might not match the user intent, e.g. ``` root [0] int i = 1; root [1] (bool)i (bool) true root [2] bool(i) ROOT_prompt_1:1:5: warning: redundant parentheses surrounding declarator [-Wredundant-parens] bool(i) ^~~ (bool) false ``` For more information see http://github.com/root-project/issues/8304. Closes issue #8304.

view details

Bertrand Bellenot

commit sha 901018c7fd1346c5fa14a91c21c8c838365e00f9

Disable the __CUDACC__ macro definition with latest Visual Studio Disable the silly workaround for cling not being able to parse the STL headers anymore after the update of Visual Studio v16.7.0. Works now with the upgrade of LLVM and Visual Studio 16.10.3. This workaround had side effects when trying to use code supporting CUDA (e.g. boost) inside the interpreter.

view details

Bertrand Bellenot

commit sha 8d5ab809ecbfe9586267d0a92d5449fecd7c1a1b

Use C++ syntax (and not the CMake one)

view details

Bertrand Bellenot

commit sha 95ab06f44dca68f3046f95bc0a3ed65dd93bf4b0

Replace the __CUDACC__ preprocessor macro by _HAS_CONDITIONAL_EXPLICIT=0 The `__CUDACC__` preprocessor define macro is not needed anymore (thanks to Axel), but the `_HAS_CONDITIONAL_EXPLICIT=0` one still is.

view details

push time in 2 months