your (full) in projects: third_party - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:your (Results 1 – 25 of 10745) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...430

/third_party/typescript/src/deprecatedCompat/
D	deprecations.ts	20 … "Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation cont… 22 …/ @deprecated Use `factory.createNodeArray` or the factory supplied by your transformation conte… 25 …/ @deprecated Use `factory.createNumericLiteral` or the factory supplied by your transformation … 28 …/ @deprecated Use `factory.createBigIntLiteral` or the factory supplied by your transformation c… 31 …/ @deprecated Use `factory.createStringLiteral` or the factory supplied by your transformation c… 34 …/ @deprecated Use `factory.createStringLiteralFromNode` or the factory supplied by your transfor… 37 …/ @deprecated Use `factory.createRegularExpressionLiteral` or the factory supplied by your trans… 40 …/ @deprecated Use `factory.createLoopVariable` or the factory supplied by your transformation co… 43 …/ @deprecated Use `factory.createUniqueName` or the factory supplied by your transformation cont… 46 …/** @deprecated Use `factory.createPrivateIdentifier` or the factory supplied by your transformati… [all …]
/third_party/typescript/tests/baselines/reference/
D	doYouNeedToChangeYourTargetLibraryES2015.errors.txt	1 …ts(3,26): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 2 …ts(4,30): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 3 …ts(5,35): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 4 …ts(6,35): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 5 …ts(7,24): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 6 …ts(8,45): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 7 …ts(9,35): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 8 …s(10,33): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 9 …s(11,28): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 10 …s(12,38): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… [all …]
D	doYouNeedToChangeYourTargetLibraryES2016Plus.errors.txt	1 …perty 'includes' does not exist on type 'string[]'. Do you need to change your target library? Try… 2 …0: Property 'padStart' does not exist on type '""'. Do you need to change your target library? Try… 3 …550: Property 'padEnd' does not exist on type '""'. Do you need to change your target library? Try… 4 …values' does not exist on type 'ObjectConstructor'. Do you need to change your target library? Try… 5 …ntries' does not exist on type 'ObjectConstructor'. Do you need to change your target library? Try… 6 …iptors' does not exist on type 'ObjectConstructor'. Do you need to change your target library? Try… 7 …atToParts' does not exist on type 'DateTimeFormat'. Do you need to change your target library? Try… 8 …s(11,21): error TS2583: Cannot find name 'Atomics'. Do you need to change your target library? Try… 9 …error TS2583: Cannot find name 'SharedArrayBuffer'. Do you need to change your target library? Try… 10 …finally' does not exist on type 'Promise<unknown>'. Do you need to change your target library? Try… [all …]
D	bigintWithoutLib.errors.txt	1 ….ts(4,25): error TS2583: Cannot find name 'BigInt'. Do you need to change your target library? Try… 2 ….ts(5,13): error TS2583: Cannot find name 'BigInt'. Do you need to change your target library? Try… 3 …b.ts(6,5): error TS2583: Cannot find name 'BigInt'. Do you need to change your target library? Try… 4 ….ts(7,13): error TS2583: Cannot find name 'BigInt'. Do you need to change your target library? Try… 6 ….ts(8,13): error TS2583: Cannot find name 'BigInt'. Do you need to change your target library? Try… 13 …8): error TS2583: Cannot find name 'BigInt64Array'. Do you need to change your target library? Try… 21 …9): error TS2583: Cannot find name 'BigInt64Array'. Do you need to change your target library? Try… 22 …9): error TS2583: Cannot find name 'BigInt64Array'. Do you need to change your target library? Try… 23 …9): error TS2583: Cannot find name 'BigInt64Array'. Do you need to change your target library? Try… 24 …): error TS2583: Cannot find name 'BigUint64Array'. Do you need to change your target library? Try… [all …]
D	modularizeLibrary_ErrorFromUsingES6FeaturesWithOnlyES5Lib.errors.txt	1 …y 'from' does not exist on type 'ArrayConstructor'. Do you need to change your target library? Try… 2 …ib.ts(10,13): error TS2583: Cannot find name 'Map'. Do you need to change your target library? Try… 4 …550: Property 'sign' does not exist on type 'Math'. Do you need to change your target library? Try… 5 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 6 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 8 …ts(36,1): error TS2583: Cannot find name 'Reflect'. Do you need to change your target library? Try… 9 …: Property 'flags' does not exist on type 'RegExp'. Do you need to change your target library? Try… 10 …roperty 'includes' does not exist on type 'string'. Do you need to change your target library? Try… 11 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 12 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… [all …]
D	importHelpersNoHelpers.errors.txt	1 …r named '__exportStar' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 2 …lper named '__extends' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 3 …per named '__decorate' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 4 …per named '__metadata' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 5 …helper named '__param' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 6 …elper named '__assign' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 7 … helper named '__rest' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 13 …r named '__exportStar' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 17 …lper named '__extends' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. 23 …per named '__decorate' which does not exist in 'tslib'. Consider upgrading your version of 'tslib'. [all …]
D	forwardDeclaredCommonTypes01.errors.txt	1 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 2 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 3 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 4 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 5 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 6 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 7 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 21 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 24 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… 26 …efers to a type, but is being used as a value here. Do you need to change your target library? Try… [all …]
/third_party/skia/site/docs/dev/contrib/
D	submit.md	10 git config --global user.name "Your Name" 15 First create a branch for your changes: 22 After making your changes, create a commit 29 If your branch gets out of date, you will need to update it: 45 Unit tests are best, but if your change touches rendering and you can't think of 47 your change is in the GPU code, you may not be able to write it as part of the 53 For your code to be accepted into the codebase, you must complete the 58 and send it to us as described on that page. Add your (or your organization's) 59 name and contact info to the AUTHORS file as a part of your CL. 77 appropriate reviewers for your change. The button is located here: [all …]
/third_party/flutter/skia/site/dev/contrib/
D	submit.md	10 git config --global user.name "Your Name" 16 First create a branch for your changes: 23 After making your changes, create a commit 30 If your branch gets out of date, you will need to update it: 47 Unit tests are best, but if your change touches rendering and you can't think of 48 an automated way to verify the results, consider writing a GM test. Also, if your 55 For your code to be accepted into the codebase, you must complete the 61 and send it to us as described on that page. Add your (or your organization's) 62 name and contact info to the AUTHORS file as a part of your CL. 80 Use `git cl` to upload your change: [all …]
/third_party/python/Doc/howto/
D	pyporting.rst	12 use, it is good to have your project available for both major releases of 29 To make your project be single-source Python 2/3 compatible, the basic steps 36 #. Use Futurize_ (or Modernize_) to update your code (e.g. ``python -m pip install future``) 37 #. Use Pylint_ to help make sure you don't regress on your Python 3 support 39 #. Use caniusepython3_ to find out which of your dependencies are blocking your 41 #. Once your dependencies are no longer blocking you, use continuous integration 44 #. Consider using optional static type checking to make sure your type usage 45 works in both Python 2 & 3 (e.g. use mypy_ to check your typing under both 59 today! Even if your dependencies are not supporting Python 3 yet that does 60 not mean you can't modernize your code now to support Python 3. Most changes [all …]
/third_party/boost/libs/hana/
D	CONTRIBUTING.md	10 If your contribution is a bug fix, you should name your branch `bugfix/xxx`; 11 for a feature, it should be `feature/xxx`. Otherwise, just use your good 14 3. Do your modifications on that branch. Except for special cases, your 17 4. Make sure your modifications did not break anything by building and 26 5. Commit your changes. Your commit message should start with a one line 28 of your modifications following in subsequent paragraphs or bullet points. 29 Please limit your lines to about 78 characters in commit messages, since 30 it makes the output easier to read in `git log`. Also, starting your commit 45 _logical_ commit. If your contribution has several logical commits, 47 6. Push the changes to your fork (`git push origin your_branch`). [all …]
/third_party/node/deps/npm/man/man7/
D	developers.7	7 your project\. 12 that your users will do to install your program\. 39 Even if you never publish your package, you can still get a lot of 59 You need to have a \fBpackage\.json\fP file in the root of your project to do 67 This should be a string that identifies your project\. Please do not 70 node (or whatever else) that your program requires, and it's pretty 72 It does not necessarily need to match your github repository name\. 79 Specify the versions of node (or whatever else) that your program 93 If you have a single module that serves as the entry point to your 104 You can use \fBnpm init\fP in the root of your package in order to get you [all …]
/third_party/cJSON/tests/unity/docs/
D	UnityConfigurationGuide.md	33 options to your compiler through command line compiler flags. Even if you're 35 configuration, there will be a place somewhere in your project to configure 36 defines for your compiler. 37 2. You can create a custom `unity_config.h` configuration file (present in your 39 specific to your target. All you must do is define `UNITY_INCLUDE_CONFIG_H` and 54 number of features for helping to adjust itself to match your required integer 60 The first thing that Unity does to guess your types is check `stdint.h`. 62 learn a lot about your system. It's possible you don't want it to do this 63 (um. why not?) or (more likely) it's possible that your system doesn't 74 The second attempt to guess your types is to check `limits.h`. Some compilers [all …]
/third_party/libusb/
D	PORTING	13 your target platform. 15 In terms of USB I/O, your backend provides functionality to submit 17 layers, based on the async interface). Your backend must also provide 20 Your backend must also provide an event handling function to "reap" ongoing 30 For libusb to work, your event handling function obviously needs to be called 31 at various points in time. Your backend must provide a set of file descriptors 36 which can be passed to poll(). If something similar is not true for your 48 Your implementations of these functions will need to call various internal 52 You probably want to skim over all the documentation before starting your 64 1. Modify configure.ac to detect your platform appropriately (see the OS_LINUX [all …]
/third_party/flutter/skia/third_party/externals/angle2/doc/
D	ContributingCode.md	10 ## Get your code ready 18 …* You _must_ update the build files with your changes. See `src/libGLESv2.gni` and `src/compiler.g… 21 …in shell run `generate_parser.sh` in `src/compiler/translator` and update your CL. Do not edit the… 26 …* ANGLE uses trybots to test on a variety of platforms. Please run your changes against our bots a… 27 * Upload your change (see [Making changes](#making-changes)). 31 …* If a failure is unexpected, or seems likely unrelated to your change, ask an ANGLE project membe… 37 …* If you aren't a browser developer, you should be able to drop your compiled DLLs into a Chrome i… 38 …* If your code isn't covered by an existing test, you are strongly encouraged to add new test co… 40 …* If you are submitting a performance fix, test your code with `angle_perftests` and add a new per… 50 …3. If you've never submitted code before, you must add your (or your organization's) name and cont… [all …]
/third_party/node/deps/npm/docs/content/using-npm/
D	developers.md	14 your project. 19 that your users will do to install your program. 39 Even if you never publish your package, you can still get a lot of 58 You need to have a `package.json` file in the root of your project to do 65 This should be a string that identifies your project. Please do not 68 node (or whatever else) that your program requires, and it's pretty 71 It does not necessarily need to match your github repository name. 79 Specify the versions of node (or whatever else) that your program 93 If you have a single module that serves as the entry point to your 102 You can use `npm init` in the root of your package in order to get you [all …]
/third_party/unity/docs/
D	UnityConfigurationGuide.md	33 options to your compiler through command line compiler flags. Even if you're 35 configuration, there will be a place somewhere in your project to configure 36 defines for your compiler. 37 2. You can create a custom `unity_config.h` configuration file (present in your 39 specific to your target. All you must do is define `UNITY_INCLUDE_CONFIG_H` and 58 number of features for helping to adjust itself to match your required integer 64 The first thing that Unity does to guess your types is check `stdint.h`. 66 learn a lot about your system. It's possible you don't want it to do this 67 (um. why not?) or (more likely) it's possible that your system doesn't 80 The second attempt to guess your types is to check `limits.h`. Some compilers [all …]
/third_party/grpc/src/objective-c/
D	README.md	11 - [Write your API declaration in proto format](#write-protos) 12 - [Integrate a proto library in your project](#cocoapods) 13 - [Use the generated library in your code](#use) 21 ## Write your API declaration in proto format 27 ## Integrate a proto library in your project 31 You need to create a Podspec file for your proto library. You may simply copy the following example 32 to the directory where your `.proto` files are located, updating the name, version and license as 34 you place this podspec relative to your Podfile. 41 s.authors = { '<your name>' => '<your email>' } 56 pods_root = '<path to your Podfile>/Pods' [all …]
/third_party/flatbuffers/
D	CONTRIBUTING.md	8 Before we can use your code, you must sign the 11 copyright to your changes, even after your contribution becomes part of our 12 codebase, so we need your permission to use and distribute your code. We also 14 know that your code infringes on other people's patents. You don't have to sign 15 the CLA until after you've submitted your code for review and a member has 16 approved it, but you must do it before we can put your code into our codebase. 18 us first through the issue tracker with your idea so that we can help out and 34 * If your PR consists of multiple commits which are successive improvements / 35 fixes to your first commit, consider squashing them into a single commit 36 (`git rebase -i`) such that your PR is a single commit on top of the current
/third_party/flatbuffers/docs/source/
D	CONTRIBUTING.md	8 Before we can use your code, you must sign the 11 copyright to your changes, even after your contribution becomes part of our 12 codebase, so we need your permission to use and distribute your code. We also 14 know that your code infringes on other people's patents. You don't have to sign 15 the CLA until after you've submitted your code for review and a member has 16 approved it, but you must do it before we can put your code into our codebase. 18 us first through the issue tracker with your idea so that we can help out and 34 * If your PR consists of multiple commits which are successive improvements / 35 fixes to your first commit, consider squashing them into a single commit 36 (`git rebase -i`) such that your PR is a single commit on top of the current
/third_party/node/deps/npm/man/man5/
D	package-json.5	6 This document is all you need to know about what's required in your package\.json 13 If you plan to publish your package, the \fImost\fR important things in your 17 plan to publish your package, the name and version fields are optional\. 19 The name is what your thing is called\. 57 If you plan to publish your package, the \fImost\fR important things in your 61 plan to publish your package, the name and version fields are optional\. 70 Put a description in it\. It's a string\. This helps people discover your 75 discover your package as it's listed in \fBnpm search\fP\\|\. 89 The url to your project's issue tracker and / or the email address to which 91 with your package\. [all …]
/third_party/mesa3d/docs/
D	repository.rst	26 #. Install the Git software on your computer if needed. 33 #. Later, you can update your tree from the upstream repository with: 59 - Use `GitLab <https://gitlab.freedesktop.org/>`__ to create your 63 - You'll have to rely on another Mesa developer to push your initial 68 to give you access to merge your own code. 70 Pushing code to your GitLab account via HTTPS 77 to push over HTTPS if ssh does not suit your needs. In this case, create 82 … git remote set-url --push origin https://USER:TOKEN@gitlab.freedesktop.org/your~user~name/mesa.git 89 want to enable automatic CR/LF conversion in your local copy of the 133 would rebase your branch prior to merging with main. But for small [all …]
/third_party/typescript_eslint/
D	CONTRIBUTING.md	9 … version of our packages. We release every week, so there's a good chance your issue might have al… 25 Please refrain from commenting on old, closed issues and PRs. Your issue is rarely related enough t… 27 …that nobody else can discover your comments. Raise an issue and reference the commit instead so th… 43 ### Validating Your Changes 45 …n on every PR. You must pass all of the checks for us to consider merging your PR. Here is a list … 47 - Ensure your code is properly formatted. 52 - Ensure your changes are adequately tested. 55 …t should also comment on your PR with the percentage, as well as links to the line-by-line coverag… 67 Once your changes are ready, you can raise a PR. The title of your PR should match the following fo… 85 Within the body of your PR, make sure you reference the issue that you have worked on, as well as p… [all …]
/third_party/flutter/skia/third_party/externals/sdl/docs/
D	README-macosx.md	30 should compile your application the same way. 45 - If you register your own NSApplicationDelegate (using [NSApp setDelegate:]), 49 file with the app. To solve these issues, put the following code in your 80 An existing autoconf/automake build system for your SDL app has good chances 87 your Makefile.am: 100 name as specified in your configure.in file. 102 If your project builds more than one application, you will have to do a bit 103 more. For each of your target applications, you need a separate rule. 106 rule to your Makefile.am: 122 there are some more things you should do before shipping your product... [all …]
/third_party/lwip/src/core/
D	init.c	86 #error "BYTE_ORDER is not defined, you have to define it in your cc.h" 89 …adcast filter per pcb on recv operations, you have to define IP_SOF_BROADCAST=1 in your lwipopts.h" 92 #error "If you want to use UDP Lite, you have to define LWIP_UDP=1 in your lwipopts.h" 95 #error "If you want to use DHCP, you have to define LWIP_UDP=1 in your lwipopts.h" 98 … use LWIP_MULTICAST_TX_OPTIONS, you have to define LWIP_UDP=1 and/or LWIP_RAW=1 in your lwipopts.h" 101 #error "If you want to use DNS, you have to define LWIP_UDP=1 in your lwipopts.h" 105 #error "If you want to use ARP Queueing, you have to define MEMP_NUM_ARP_QUEUE>=1 in your lwipopts.… 108 #error "If you want to use RAW, you have to define MEMP_NUM_RAW_PCB>=1 in your lwipopts.h" 111 #error "If you want to use UDP, you have to define MEMP_NUM_UDP_PCB>=1 in your lwipopts.h" 114 #error "If you want to use TCP, you have to define MEMP_NUM_TCP_PCB>=1 in your lwipopts.h" [all …]

12 3 4 5 6 7 8 9 10 >>...430